Re: [PATCH v1 0/4] virtio-msg transport layer

"Michael S. Tsirkin" <[email protected]> Wed, 25 Feb 2026 05:08:59 -0500
Newsgroups dev.linux.lists.virtio-comment
Message-ID <[email protected]>
On Wed, Feb 25, 2026 at 10:01:45AM +0000, Bertrand Marquis wrote:
> Hi Michael,
> 
> [snip]
> 
> >>>>
> >>>>
> >>>> I frankly expect an ARM FF-A bus binding transport section in virtio-spec.
> >>>> So that device and driver can inter-operate implemented by two different entities.
> >>>> Only virtio level messages do not seem sufficient.
> >>>
> >>> I agree at least one should be shown at least as an rfc.
> >>
> >> Here is a link to the current virtio message bus over FF-A specification:
> >> https://developer.arm.com/documentation/den0153/0101/
> >>
> >> 1.0 Alpha 1 version in sync with this version of the virtio message spec will be released later today, you will be redirected to
> >> 1.0 Alpha 0 version until it is  which is in sync with the previous RFC we sent.
> >>
> >> Regards
> >> Bertrand
> >>
> >>
> >> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
> >
> >
> > thanks. pls include that in the series as [PATCH RFC 5/4]
> >
> 
> We are not planning to have this included in the virtio specification but maintained by arm as an independent specification.
> FF-A is an arm specification and as such virtio message bus over FF-A is arm specific.
> 
> We can reference it as a bus specification example in the virtio specification if you want (as an external link).

Surely, you should. 


But for a variety of reasons, including the fact that they should be
developed in lockstep, and others, please include it in the list with
"RFC  do not apply" subject.


> Regards
> Bertrand
> 
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.