@@ -24,11 +24,6 @@ some of which will be reusable and general purpose. Other bus implementations
2424might be unique to a given situation, for example only used by a PCIe card
2525and its driver.
2626
27- How much of the bus level should be described in the virtio spec is one item
28- we wish to discuss. This draft takes a middle approach by describing the bus
29- level and defining some standard bus level messages that MAY be used by the bus.
30- It also describes a range of bus messages that are implementation dependent.
31-
3227The standard bus messages are an effort to avoid different bus implementations
3328doing the same thing in different ways for no good reason. However the
3429different environments will require different things. Instead of trying to
@@ -78,30 +73,29 @@ Spec Functional:
7873 when parallel outstanding requests are possible
7974* Made the 8 byte fields align to 8 byte offsets.
8075 This effects the {SET,GET}_VQUEUE messages
76+ * Many conformance cases have been tightened.
8177
8278Spec Editorial:
79+ * Major restructure to better align with virtio spec
80+ * Conformance model now matches other transports
81+ * Use C structures to define messages instead of tables
8382* Added a section to describe how responses are matched to requests
8483 This includes the use of the new token field
85- * Redefined / better described error handling between to transport and bus
84+ * Redefined / better described error handling between transport and bus
8685 layers to eliminate the need for the bus to generate fake response messages
87- * Included editorial feedback from Matias
88- * Included much of Peter's editorial feedback, some items are still pending
86+ * Included editorial feedback from RFC2
8987
9088Eco-system:
91- * Add virtio-msg-loopback demo
92- * Arm has published the first draft of the virtio-msg over FFA spec
93- * virtio-msg over FFA has been demonstrated with both Trusty and OP-TEE
89+ * Added virtio-msg-loopback demo
90+ * Arm has published the first draft of the virtio-msg over FFA spec [6]
91+ * virtio-msg over FFA has been demonstrated with both Trusty and OP-TEE
9492 secure world
95- * QEMU RFCv1 has been sent
96- * LKML RFCs have been sent
97-
98- This series is a work in progress and we acknowledge at least the following
99- issues we need to work on:
93+ * LKML RFC has been sent [7]
94+ * QEMU RFC has been sent [8]
10095
101- * Better conformance documentation
102- * Moving the Arm ltd virtio-msg FFA spec from Alpha to at least Beta level
103- * Publish virtio-msg-amp data structures and messages somewhere
104- * Align implementations to this version and send PATCH v1 (non-rfc)
96+ This is the first non-RFC patch series. The known short comings have been
97+ addressed. We ask for review in earnest on this series and thank you for
98+ any feedback you can provide.
10599
106100Background info and work in progress implementations:
107101* HVAC project page with intro slides [1]
@@ -115,11 +109,14 @@ two hardware systems running:
115109* AMD x86 + AMD Arm Versal connected via PCIe
116110* ST STM32MP157 A7 Linux using virtio-i2c provided by M4 Zephyr
117111
118- Please note that although the demos work, not all of them have been aligned
112+ Please note that although the demos work, a few have not been aligned
119113with this version of the spec.
120114
121115[1] https://linaro.atlassian.net/wiki/spaces/HVAC/overview
122116[2] https://github.com/wmamills/hvac-demo
123117[3] https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/linux.git/log/?h=virtio/msg
124- [4] https://github.com/edgarigl/qemu/commits/edgar/virtio-msg-new
118+ [4] https://github.com/edgarigl/qemu/commits/edgar/virtio-msg-rfc/
125119[5] https://github.com/arnopo/open-amp/commits/virtio-msg/
120+ [6] https://documentation-service.arm.com/static/68f647791134f773ab3f0a7c
121+ [7] https://lore.kernel.org/all/cover.1753865268.git.viresh.kumar@linaro.org/
122+ [8] https://mail.gnu.org/archive/html/qemu-devel/2025-10/msg07438.html
0 commit comments