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:
* virtio-msg-ffa based on Arm's Virtio Message Bus over FF-A specification [6]
for use between:
* normal world and secure world
* host and VM or VM to VM
* Can be used w/ or with out a hypervisor
* Any Hypervisor that implements FF-A can be used
* We have this working with pKVM and Xen
* We have this working with Trusty and OP-TEE
* virtio-msg-amp for use between heterogenous systems
* The main processors and its co-processors on an AMP SOC
* Two or more systems connected via PCIe
* Minimal requirements: bi-directional interrupts and
at least one shared memory area
* hvac-demo has 2 demos of this
* This is working on two hardware platforms
* virtio-msg-loopback for userspace implemented devices
* Allows user space to provide devices to its own kernel
* This is similar to fuse, cuse or loopback block devices but for virtio
* hvac-demo has a demo
We also anticipate a few more:
* virtio-msg-xen specific to Xen
* Usable on any Xen system (including x86 where FF-A does not exist)
* Using Xen events and page grants
This series keeps 16-bit dev_num values per bus instance; deployments that need
more than roughly 65k devices can scale by using multiple bus instances.
Changes since v1 (virtio-msg-patch1):
First, thank you for the detailed comments and broad interest on v1.
This revision incorporates review feedback from Peter Hilber, Demi Marie
Obenour, Parav Pandit, Andrei Homescu, Manos Pitsidianakis, Michael S.
Tsirkin, Bill Mills, and HVAC group discussion.
Highlights of the changes since v1:
* Finalized the common transport message model:
* keep the 8-byte common header
* keep 16-bit device numbers per bus instance and a 16-bit msg_size field
* note that deployments needing more than roughly 65k devices can scale by
using multiple bus instances
* clarify common message-ID encoding and validation boundaries
* define request completion more precisely: a valid supported request
completes with exactly one protocol response or a transport-visible failure
* clarify request/response correlation and token handling, including the
rule that devices echo the request token while the bus may rewrite tokens
internally for correlation
* preserve per driver/device request ordering while still allowing
bus-correlated out-of-order responses and events
* Clarified bus versus transport responsibilities and enumeration:
* keep GET_DEVICE_INFO as a driver-issued transport message, and GET_DEVICES,
PING, and EVENT_DEVICE as optional bus messages
* require bus messages to use dev_num = 0
* bus implementations must expose only validated device numbers, may expose
zero devices, and should delay device-number reuse to reduce races
* EVENT_DEVICE is defined as a bus-originated ADDED/REMOVED hotplug event
* tighten GET_DEVICES enumeration semantics, including empty-bitmap cases and
guaranteed forward progress
* Tightened initialization and feature negotiation:
* use transport revision terminology consistently
* keep GET_DEVICE_INFO as the only transport message used for early discovery
* align the rest of initialization with the core virtio flow through reset,
status progression, feature negotiation, FEATURES_OK verification, and
DRIVER_OK
* keep transport feature bits separate from device feature negotiation
* define GET_DEVICE_FEATURES as reporting the feature blocks offered by the
device
* require GET_DEVICE_INFO to report enough feature blocks to cover all
offered feature bits and bound max_virtqueues to 65536
* define SET_DRIVER_FEATURES as addressed-block updates carrying the subset
chosen by the driver, which may be built up across multiple requests before
FEATURES_OK
* keep FEATURES_OK as the point where the device accepts or rejects the
negotiated set
* make GET_SHM mandatory for devices to implement while keeping driver use
optional, and align the shared-memory identifier semantics with core virtio
* Aligned configuration, status, and notification behavior with core virtio:
* align GET_CONFIG, SET_CONFIG, EVENT_CONFIG, and device status handling more
closely with the core virtio model
* keep VIRTIO_MSG_F_STRICT_CONFIG_GENERATION only as optional strict-profile
SET_CONFIG mismatch enforcement
* define nonzero SET_CONFIG writes as all-or-nothing and rejected writes as
length = 0 with no payload
* limit EVENT_CONFIG status notifications to device-originated asynchronous
status changes
* make polling-only operation explicit, with EVENT_AVAIL and EVENT_USED used
only when the endpoints choose event-driven notification
* keep bus-side forwarding, polling, or synthesized notification delivery
transparent to the transport-visible model
* Refined virtqueue and reset semantics:
* clarify queue-state transitions, SET_VQUEUE update behavior, and invalid
reconfiguration cases
* make SET_VQUEUE and RESET_VQUEUE reject cases deterministic no-op empty
responses
* define deterministic GET_VQUEUE zero-sentinel responses for unavailable,
unimplemented, and out-of-range queues
* define local admin virtqueue field semantics and the EVENT_AVAIL
notification-data encoding more precisely
* clarify reset-completion checks without duplicating the core virtio reset
rules
* Improved document quality:
* reworked the chapter to better match existing virtio specification style
* removed duplicated or ambiguous requirements
* fixed label paths, direct field references, punctuation, and ambiguous
wording
* added informative known bus implementation examples
* completed conformance coverage for driver, device, and bus clauses
* normalized punctuation and wording for consistency with the rest of the spec
Open topics and ongoing discussion:
* Out-of-order/performance extensions:
We kept the baseline behavior simple in this revision. If clear performance
benefit is demonstrated, we are open to introducing an optional feature-bit
based extension in a follow-up patch set.
* Graceful device removal sequencing:
Current direction is to handle graceful-remove sequencing in bus-specific
specifications. We welcome feedback on whether any additional transport-level
guidance would be useful.
* Transport scope and mapping guidance:
Discussion is still ongoing on transport-vs-bus binding scope, response
status modeling, and mapping guidance for mmio/pci/vhost-user/KVM userspace
cases. We are collecting reviewer input before deciding on follow-up text.
* Potential virtio-msg over virtqueues for PCI/MMIO:
This is still early discussion, including whether admin virtqueues should be
used or extended for this purpose. There is no consensus yet, and we are
continuing design exploration.
Eco-system:
* Added virtio-msg-loopback demo
* Arm has published the Virtio Message Bus over FF-A specification [6]
* virtio-msg over FF-A has been demonstrated with both Trusty and OP-TEE
secure world
* LKML RFC has been sent [7]
* QEMU RFC has been sent [8]
This is v2 of the first non-RFC patch series. We are grateful for the review
feedback and interest received on v1, and we ask for continued review on this
revision.
Background info and work in progress implementations:
* HVAC project page with intro slides [1]
* HVAC demo repo w/ instructions in README.md [2]
* Kernel w/ virtio-msg common level and ffa support [3]
* QEMU w/ support for one form of virtio-msg-amp [4]
* Portable RTOS library w/ one form of virtio-msg-amp [5]
In addition to the QEMU system based demos in the hvac-demo repo, we also have
two hardware systems running:
* AMD x86 + AMD Arm Versal connected via PCIe
* ST STM32MP157 A7 Linux using virtio-i2c provided by M4 Zephyr
Please note that although the demos work, a few have not been aligned
with this version of the spec.
[1] https://linaro.atlassian.net/wiki/spaces/HVAC/overview
[2] https://github.com/wmamills/hvac-demo
[3] https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/linux.git/log/?h=vi…
[4] https://github.com/edgarigl/qemu/commits/edgar/virtio-msg-rfc/
[5] https://github.com/arnopo/open-amp/commits/virtio-msg/
[6] https://developer.arm.com/documentation/den0153/0101/
[7] https://lore.kernel.org/all/cover.1753865268.git.viresh.kumar@linaro.org/
[8] https://mail.gnu.org/archive/html/qemu-devel/2025-10/msg07438.html
Bertrand Marquis (6):
virtio-msg: add new command for bus normative
virtio-msg: Add the FF-A bus bibliography reference
virtio-msg: Add virtio-msg, a message based virtio transport layer
virtio-msg: link virtio-msg content
virtio-msg: add conformance entries in conformance chapter
virtio-msg: add message transport to core references
commands.tex | 3 +-
conformance.tex | 97 ++-
content.tex | 18 +-
introduction.tex | 6 +-
transport-msg.tex | 2071 +++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 2185 insertions(+), 10 deletions(-)
create mode 100644 transport-msg.tex
--
2.53.0
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:
* virtio-msg-ffa based on Arm's Virtio Message Bus over FF-A specification [6]
for use between:
* normal world and secure world
* host and VM or VM to VM
* Can be used w/ or with out a hypervisor
* Any Hypervisor that implements FF-A can be used
* We have this working with pKVM and Xen
* We have this working with Trusty and OP-TEE
* virtio-msg-amp for use between heterogenous systems
* The main processors and its co-processors on an AMP SOC
* Two or more systems connected via PCIe
* Minimal requirements: bi-directional interrupts and
at least one shared memory area
* hvac-demo has 2 demos of this
* This is working on two hardware platforms
* virtio-msg-loopback for userspace implemented devices
* Allows user space to provide devices to its own kernel
* This is similar to fuse, cuse or loopback block devices but for virtio
* hvac-demo has a demo
We also anticipate a few more:
* virtio-msg-xen specific to Xen
* Usable on any Xen system (including x86 where FF-A does not exist)
* Using Xen events and page grants
This series keeps 16-bit dev_num values per bus instance; deployments that need
more than roughly 65k devices can scale by using multiple bus instances.
Changes since v1 (virtio-msg-patch1):
First, thank you for the detailed comments and broad interest on v1.
This revision incorporates review feedback from Peter Hilber, Demi Marie
Obenour, Parav Pandit, Andrei Homescu, Manos Pitsidianakis, Michael S.
Tsirkin, Bill Mills, and HVAC group discussion.
Highlights of the changes since v1:
* Finalized the common transport message model:
* keep the 8-byte common header
* keep 16-bit device numbers per bus instance and a 16-bit msg_size field
* note that deployments needing more than roughly 65k devices can scale by
using multiple bus instances
* clarify common message-ID encoding and validation boundaries
* define request completion more precisely: a valid supported request
completes with exactly one protocol response or a transport-visible failure
* clarify request/response correlation and token handling, including the
rule that devices echo the request token while the bus may rewrite tokens
internally for correlation
* preserve per driver/device request ordering while still allowing
bus-correlated out-of-order responses and events
* Clarified bus versus transport responsibilities and enumeration:
* keep GET_DEVICE_INFO as a driver-issued transport message, and GET_DEVICES,
PING, and EVENT_DEVICE as optional bus messages
* require bus messages to use dev_num = 0
* bus implementations must expose only validated device numbers, may expose
zero devices, and should delay device-number reuse to reduce races
* EVENT_DEVICE is defined as a bus-originated ADDED/REMOVED hotplug event
* tighten GET_DEVICES enumeration semantics, including empty-bitmap cases and
guaranteed forward progress
* Tightened initialization and feature negotiation:
* use transport revision terminology consistently
* keep GET_DEVICE_INFO as the only transport message used for early discovery
* align the rest of initialization with the core virtio flow through reset,
status progression, feature negotiation, FEATURES_OK verification, and
DRIVER_OK
* keep transport feature bits separate from device feature negotiation
* define GET_DEVICE_FEATURES as reporting the feature blocks offered by the
device
* require GET_DEVICE_INFO to report enough feature blocks to cover all
offered feature bits and bound max_virtqueues to 65536
* define SET_DRIVER_FEATURES as addressed-block updates carrying the subset
chosen by the driver, which may be built up across multiple requests before
FEATURES_OK
* keep FEATURES_OK as the point where the device accepts or rejects the
negotiated set
* make GET_SHM mandatory for devices to implement while keeping driver use
optional, and align the shared-memory identifier semantics with core virtio
* Aligned configuration, status, and notification behavior with core virtio:
* align GET_CONFIG, SET_CONFIG, EVENT_CONFIG, and device status handling more
closely with the core virtio model
* keep VIRTIO_MSG_F_STRICT_CONFIG_GENERATION only as optional strict-profile
SET_CONFIG mismatch enforcement
* define nonzero SET_CONFIG writes as all-or-nothing and rejected writes as
length = 0 with no payload
* limit EVENT_CONFIG status notifications to device-originated asynchronous
status changes
* make polling-only operation explicit, with EVENT_AVAIL and EVENT_USED used
only when the endpoints choose event-driven notification
* keep bus-side forwarding, polling, or synthesized notification delivery
transparent to the transport-visible model
* Refined virtqueue and reset semantics:
* clarify queue-state transitions, SET_VQUEUE update behavior, and invalid
reconfiguration cases
* make SET_VQUEUE and RESET_VQUEUE reject cases deterministic no-op empty
responses
* define deterministic GET_VQUEUE zero-sentinel responses for unavailable,
unimplemented, and out-of-range queues
* define local admin virtqueue field semantics and the EVENT_AVAIL
notification-data encoding more precisely
* clarify reset-completion checks without duplicating the core virtio reset
rules
* Improved document quality:
* reworked the chapter to better match existing virtio specification style
* removed duplicated or ambiguous requirements
* fixed label paths, direct field references, punctuation, and ambiguous
wording
* added informative known bus implementation examples
* completed conformance coverage for driver, device, and bus clauses
* normalized punctuation and wording for consistency with the rest of the spec
Open topics and ongoing discussion:
* Out-of-order/performance extensions:
We kept the baseline behavior simple in this revision. If clear performance
benefit is demonstrated, we are open to introducing an optional feature-bit
based extension in a follow-up patch set.
* Graceful device removal sequencing:
Current direction is to handle graceful-remove sequencing in bus-specific
specifications. We welcome feedback on whether any additional transport-level
guidance would be useful.
* Transport scope and mapping guidance:
Discussion is still ongoing on transport-vs-bus binding scope, response
status modeling, and mapping guidance for mmio/pci/vhost-user/KVM userspace
cases. We are collecting reviewer input before deciding on follow-up text.
* Potential virtio-msg over virtqueues for PCI/MMIO:
This is still early discussion, including whether admin virtqueues should be
used or extended for this purpose. There is no consensus yet, and we are
continuing design exploration.
Eco-system:
* Added virtio-msg-loopback demo
* Arm has published the Virtio Message Bus over FF-A specification [6]
* virtio-msg over FF-A has been demonstrated with both Trusty and OP-TEE
secure world
* LKML RFC has been sent [7]
* QEMU RFC has been sent [8]
This is v2 of the first non-RFC patch series. We are grateful for the review
feedback and interest received on v1, and we ask for continued review on this
revision.
Background info and work in progress implementations:
* HVAC project page with intro slides [1]
* HVAC demo repo w/ instructions in README.md [2]
* Kernel w/ virtio-msg common level and ffa support [3]
* QEMU w/ support for one form of virtio-msg-amp [4]
* Portable RTOS library w/ one form of virtio-msg-amp [5]
In addition to the QEMU system based demos in the hvac-demo repo, we also have
two hardware systems running:
* AMD x86 + AMD Arm Versal connected via PCIe
* ST STM32MP157 A7 Linux using virtio-i2c provided by M4 Zephyr
Please note that although the demos work, a few have not been aligned
with this version of the spec.
[1] https://linaro.atlassian.net/wiki/spaces/HVAC/overview
[2] https://github.com/wmamills/hvac-demo
[3] https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/linux.git/log/?h=vi…
[4] https://github.com/edgarigl/qemu/commits/edgar/virtio-msg-rfc/
[5] https://github.com/arnopo/open-amp/commits/virtio-msg/
[6] https://developer.arm.com/documentation/den0153/0101/
[7] https://lore.kernel.org/all/cover.1753865268.git.viresh.kumar@linaro.org/
[8] https://mail.gnu.org/archive/html/qemu-devel/2025-10/msg07438.html
Bertrand Marquis (6):
virtio-msg: add new command for bus normative
virtio-msg: Add the FF-A bus bibliography reference
virtio-msg: Add virtio-msg, a message based virtio transport layer
virtio-msg: link virtio-msg content
virtio-msg: add conformance entries in conformance chapter
virtio-msg: add message transport to core references
commands.tex | 3 +-
conformance.tex | 97 ++-
content.tex | 18 +-
introduction.tex | 6 +-
transport-msg.tex | 2071 +++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 2185 insertions(+), 10 deletions(-)
create mode 100644 transport-msg.tex
--
2.53.0
Hi Everyone,
With a bit of delay here is the v2 of the linux PoC:
https://github.com/bertrand-marquis/virtio-msg-spec/tree/linux-poc/v2/linux…
There is now loopback and ffa bus implementation in it and the rework of the transport after removing config_get/set support from non sleepable context.
I also did a bit or rework in the qemu patches to handle the comment and try to be less invasive in existing qemu code together with updating qemu virtio message implementation to be in sync with v2 oasis proposal.
Any comment on this is still very welcome.
For the arm_ffa patches, i will try to share them next week together with the xen branch going with it to be in a position to share a reproducible setup to do virtio between VMs.
Cheers
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.
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:
* virtio-msg-ffa based on Arm's Virtio Message Bus over FF-A specification [6]
for use between:
* normal world and secure world
* host and VM or VM to VM
* Can be used w/ or with out a hypervisor
* Any Hypervisor that implements FF-A can be used
* We have this working with pKVM and Xen
* We have this working with Trusty and OP-TEE
* virtio-msg-amp for use between heterogenous systems
* The main processors and its co-processors on an AMP SOC
* Two or more systems connected via PCIe
* Minimal requirements: bi-directional interrupts and
at least one shared memory area
* hvac-demo has 2 demos of this
* This is working on two hardware platforms
* virtio-msg-loopback for userspace implemented devices
* Allows user space to provide devices to its own kernel
* This is similar to fuse, cuse or loopback block devices but for virtio
* hvac-demo has a demo
We also anticipate a few more:
* virtio-msg-xen specific to Xen
* Usable on any Xen system (including x86 where FF-A does not exist)
* Using Xen events and page grants
This series keeps 16-bit dev_num values per bus instance; deployments that need
more than roughly 65k devices can scale by using multiple bus instances.
Changes since v1 (virtio-msg-patch1):
First, thank you for the detailed comments and broad interest on v1.
This revision incorporates review feedback from Peter Hilber, Demi Marie
Obenour, Parav Pandit, Andrei Homescu, Manos Pitsidianakis, Michael S.
Tsirkin, Bill Mills, and HVAC group discussion.
Highlights of the changes since v1:
* Finalized the common transport message model:
* keep the 8-byte common header
* keep 16-bit device numbers per bus instance and a 16-bit msg_size field
* note that deployments needing more than roughly 65k devices can scale by
using multiple bus instances
* clarify common message-ID encoding and validation boundaries
* define request completion more precisely: a valid supported request
completes with exactly one protocol response or a transport-visible failure
* clarify request/response correlation and token handling, including the
rule that devices echo the request token while the bus may rewrite tokens
internally for correlation
* preserve per driver/device request ordering while still allowing
bus-correlated out-of-order responses and events
* Clarified bus versus transport responsibilities and enumeration:
* keep GET_DEVICE_INFO as a driver-issued transport message, and GET_DEVICES,
PING, and EVENT_DEVICE as optional bus messages
* require bus messages to use dev_num = 0
* bus implementations must expose only validated device numbers, may expose
zero devices, and should delay device-number reuse to reduce races
* EVENT_DEVICE is defined as a bus-originated ADDED/REMOVED hotplug event
* tighten GET_DEVICES enumeration semantics, including empty-bitmap cases and
guaranteed forward progress
* Tightened initialization and feature negotiation:
* use transport revision terminology consistently
* keep GET_DEVICE_INFO as the only transport message used for early discovery
* align the rest of initialization with the core virtio flow through reset,
status progression, feature negotiation, FEATURES_OK verification, and
DRIVER_OK
* keep transport feature bits separate from device feature negotiation
* define GET_DEVICE_FEATURES as reporting the feature blocks offered by the
device
* require GET_DEVICE_INFO to report enough feature blocks to cover all
offered feature bits and bound max_virtqueues to 65536
* define SET_DRIVER_FEATURES as addressed-block updates carrying the subset
chosen by the driver, which may be built up across multiple requests before
FEATURES_OK
* keep FEATURES_OK as the point where the device accepts or rejects the
negotiated set
* make GET_SHM mandatory for devices to implement while keeping driver use
optional, and align the shared-memory identifier semantics with core virtio
* Aligned configuration, status, and notification behavior with core virtio:
* align GET_CONFIG, SET_CONFIG, EVENT_CONFIG, and device status handling more
closely with the core virtio model
* keep VIRTIO_MSG_F_STRICT_CONFIG_GENERATION only as optional strict-profile
SET_CONFIG mismatch enforcement
* define nonzero SET_CONFIG writes as all-or-nothing and rejected writes as
length = 0 with no payload
* limit EVENT_CONFIG status notifications to device-originated asynchronous
status changes
* make polling-only operation explicit, with EVENT_AVAIL and EVENT_USED used
only when the endpoints choose event-driven notification
* keep bus-side forwarding, polling, or synthesized notification delivery
transparent to the transport-visible model
* Refined virtqueue and reset semantics:
* clarify queue-state transitions, SET_VQUEUE update behavior, and invalid
reconfiguration cases
* make SET_VQUEUE and RESET_VQUEUE reject cases deterministic no-op empty
responses
* define deterministic GET_VQUEUE zero-sentinel responses for unavailable,
unimplemented, and out-of-range queues
* define local admin virtqueue field semantics and the EVENT_AVAIL
notification-data encoding more precisely
* clarify reset-completion checks without duplicating the core virtio reset
rules
* Improved document quality:
* reworked the chapter to better match existing virtio specification style
* removed duplicated or ambiguous requirements
* fixed label paths, direct field references, punctuation, and ambiguous
wording
* added informative known bus implementation examples
* completed conformance coverage for driver, device, and bus clauses
* normalized punctuation and wording for consistency with the rest of the spec
Open topics and ongoing discussion:
* Out-of-order/performance extensions:
We kept the baseline behavior simple in this revision. If clear performance
benefit is demonstrated, we are open to introducing an optional feature-bit
based extension in a follow-up patch set.
* Graceful device removal sequencing:
Current direction is to handle graceful-remove sequencing in bus-specific
specifications. We welcome feedback on whether any additional transport-level
guidance would be useful.
* Transport scope and mapping guidance:
Discussion is still ongoing on transport-vs-bus binding scope, response
status modeling, and mapping guidance for mmio/pci/vhost-user/KVM userspace
cases. We are collecting reviewer input before deciding on follow-up text.
* Potential virtio-msg over virtqueues for PCI/MMIO:
This is still early discussion, including whether admin virtqueues should be
used or extended for this purpose. There is no consensus yet, and we are
continuing design exploration.
Eco-system:
* Added virtio-msg-loopback demo
* Arm has published the Virtio Message Bus over FF-A specification [6]
* virtio-msg over FF-A has been demonstrated with both Trusty and OP-TEE
secure world
* LKML RFC has been sent [7]
* QEMU RFC has been sent [8]
This is v2 of the first non-RFC patch series. We are grateful for the review
feedback and interest received on v1, and we ask for continued review on this
revision.
Background info and work in progress implementations:
* HVAC project page with intro slides [1]
* HVAC demo repo w/ instructions in README.md [2]
* Kernel w/ virtio-msg common level and ffa support [3]
* QEMU w/ support for one form of virtio-msg-amp [4]
* Portable RTOS library w/ one form of virtio-msg-amp [5]
In addition to the QEMU system based demos in the hvac-demo repo, we also have
two hardware systems running:
* AMD x86 + AMD Arm Versal connected via PCIe
* ST STM32MP157 A7 Linux using virtio-i2c provided by M4 Zephyr
Please note that although the demos work, a few have not been aligned
with this version of the spec.
[1] https://linaro.atlassian.net/wiki/spaces/HVAC/overview
[2] https://github.com/wmamills/hvac-demo
[3] https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/linux.git/log/?h=vi…
[4] https://github.com/edgarigl/qemu/commits/edgar/virtio-msg-rfc/
[5] https://github.com/arnopo/open-amp/commits/virtio-msg/
[6] https://developer.arm.com/documentation/den0153/0101/
[7] https://lore.kernel.org/all/cover.1753865268.git.viresh.kumar@linaro.org/
[8] https://mail.gnu.org/archive/html/qemu-devel/2025-10/msg07438.html
Bertrand Marquis (4):
virtio-msg: add new command for bus normative
virtio-msg: Add the FF-A bus bibliography reference
virtio-msg: add conformance entries in conformance chapter
virtio-msg: propose common-spec integration text
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 | 97 ++-
content.tex | 18 +-
introduction.tex | 6 +-
transport-msg.tex | 2071 +++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 2185 insertions(+), 10 deletions(-)
create mode 100644 transport-msg.tex
--
2.34.1
Hello,
The progress has been a bit slower since past few months (because of
relocation to other stuff), but some progress was made (mostly around
AMD's AMP stuff).
- Rebased AMP Sapphire and generic PCI virtio-msg drivers (from
Edgar/Bill) over latest virtio-msg repository and made few changes
to make them work again.
- Tested the generic PCI version with help of Edgar's QEMU based
setup. I have received the physical board recently, will try to test
with that next.
- Made significant changes to both the drivers to bring them closer to
how virtio-msg FFA and loopback drivers look. Also redesigned driver
initialization and fixed how Ping implementation was working.
- Eventually the code was much cleaner and much shorter.
- The implementation was based on a simple predefined (fixed) single
producer - single consumer queue. Bill/Edgar documented [1] a new
shared memory layout earlier but was never implemented. Implemented
the first version of that for both Linux and QEMU.
--
viresh
[1] https://github.com/wmamills/hvac-demo/blob/main/notes/amp-data-structures.h
Hi Everyone,
I have a first PoC showing virtio-msg working with a loopback system between Linux kernel and Qemu.
The patches, build and run instructions can be found here:
https://github.com/bertrand-marquis/virtio-msg-spec/tree/linux-poc/v0/linux…
This is very early stage but this shows a fully functional version with rng and block validated.
I used ChatGPT help to fix issues and write part of the code (or big parts for Qemu) and this is far from upstreamable so
do not share that.
I will share a v1 in the next weeks with FF-A support but i still have some timings and DMA issues to solve.
Any comment on this is more than welcome !!
Cheers
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.
All,
Bertrand's PR#31 has been accepted to the virtio-msg-patch1 branch and the
PDF of this is available at [1] and can also be found on the repo's front page.
The format of the branch is all 76 commits on top of the original
virtio-msg-patch1 branch. In the next week I will be squashing and
rebasing this work to make a virtio-msg-patch2 branch.
If you see anything that you that should be changed, please propose a new
PR to virtio-msg-patch1 and I will fold any new commits into the patch2
branch later.
Thanks,
Bill
[1]
https://github.com/Linaro/virtio-msg-spec/releases/download/virtio-msg-patc…
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
All,
We have had a number of spam emails on this list in the past few weeks.
I set all spam authors (ever) to discard and all new subscription requests
to require moderation.
Sorry for the noise.
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Some victims of c r y p t o i n v e s t m e n t s c a m s try professional tracing services like vaulttraces.com. These companies analyze blockchain data to track the movement of funds. Having complete documentation of your transactions can improve the chances of identifying where the assets went. For assistance reach out to them on their Website;: https://vaulttraces.com/contact.html . Mail-Box: info(a)vaulttraces.com . Or WhatsApp: +1 (570) 291-8211
