Re: [PATCH RFC v2 1/1] virtio-msg: Add virtio-msg, a message based virtio transport layer

Matias Ezequiel Vara Larsen <[email protected]>
Newsgroups dev.linux.lists.virtio-comment
Message-ID <CAHYGQ0yqVSqUN3vAkr4MrMT-1eqta3u6g_LNzwDx10yGcSaXtQ@mail.gmail.com>
On Mon, Sep 1, 2025 at 11:37 AM Alex Bennée <[email protected]> wrote:
>
> Bill Mills <[email protected]> writes:
>
> > Add a new transport layer that is based on messages.
> >
> > This transport layer still uses virtqueues as the other transport layers do
> > but implements transport layer operations by sending and receiving messages
> > instead of the "MMR" reads and writes used in virtio-mmio and virtio-pci.
> >
> > This transport is useful when the device and driver are both implemented in
> > software but the trap and emulate operations of virtio-mmio and virtio-pci
> > can not be used.
> >
> > This transport is intended to be used in many situations, including:
> > * between a host processor and its co-processors
> > * between two different systems (not SMP) connected via PCIe
> > * between normal and secure worlds
> > * host to vm
> > * vm to vm
> >
> > This is an RFC and not yet intended to be merged. There are multiple
> > know issues including not conforming to virtio spec standards.
> >
> > Signed-off-by: Bill Mills <[email protected]>
> > Signed-off-by: Bertrand Marquis <[email protected]>
> > Signed-off-by: Edgar E. Iglesias <[email protected]>
> > Signed-off-by: Arnaud Pouliquen <[email protected]>
>
> Ping?
>
> I'll be around at KVM Forum if anyone has any questions about our
> use-cases. We've reviewed stuff pretty thoroughly internally but
> obviously we need to input from the wider VirtIO community before
> proposing a vote.
>

I am interested in understanding the use-case. I'll also attend the
KVM Forum. I am afraid I won't have time before we meet to read the
patches.

Matias


> --
> Alex Bennée
> Virtualisation Tech Lead @ Linaro
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.