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

Viresh Kumar <[email protected]> Wed, 4 Feb 2026 08:59:13 +0530
Newsgroups dev.linux.lists.virtio-comment
Message-ID <gntft4yvpcpiu6x7j6z4gnuyg44dq77ooae7zjgue6wir576vf@ibsu4qcwhf7b>
On 26-01-26, 11:32, Bill Mills wrote:
> This series adds the virtio-msg transport layer.
> 
> The individuals and organizations involved in this effort have had difficulty in
> using the existing virtio-transports in various situations and desire to add one
> more transport that performs its transport layer operations by sending and
> receiving messages.
> 
> Implementations of virtio-msg will normally be done in multiple layers:
> * common / device level
> * bus level
> 
> The common / device level defines the messages exchanged between the driver
> and a device. This common part should lead to a common driver holding most
> of the virtio specifics and can be shared by all virtio-msg bus implementations.
> The kernel implementation in [3] shows this separation. As with other transport
> layers, virtio-msg should not require modifications to existing virtio device
> implementations (virtio-net, virtio-blk etc). The common / device level is the
> main focus of this version of the patch series.
> 
> The virtio-msg bus level implements the normal things a bus defines
> (enumeration, dma operations, etc) but also implements the message send and
> receive operations. A number of bus implementations are envisioned,
> some of which will be reusable and general purpose. Other bus implementations
> might be unique to a given situation, for example only used by a PCIe card
> and its driver.
> 
> The standard bus messages are an effort to avoid different bus implementations
> doing the same thing in different ways for no good reason. However the
> different environments will require different things. Instead of trying to
> anticipate all needs and provide something very abstract, we think
> implementation specific messages will be needed at the bus level. Over time,
> if we see similar messages across multiple bus implementations, we will move to
> standardize a bus level message for that.
> 
> We are working on a few reusable bus implementations:
 
> Bertrand Marquis (2):
>   virtio-msg: add new command for bus normative
>   virtio-msg: add conformance entries in conformance chapter
> 
> Bill Mills (2):
>   virtio-msg: Add virtio-msg, a message based virtio transport layer
>   virtio-msg: link virtio-msg content
> 
>  commands.tex      |    3 +-
>  conformance.tex   |  105 ++-
>  content.tex       |    1 +
>  transport-msg.tex | 1640 +++++++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 1746 insertions(+), 3 deletions(-)
>  create mode 100644 transport-msg.tex

Acked-by: Viresh Kumar <[email protected]>

-- 
viresh