2025-05 Update and Notes
Summary of Month
Plans
Hold Virtio-msg Sprint before Linaro Connect in Lisbon
Do multiple presentation and demos on virtio-msg at Linaro Connect
Do a 2nd spec RFC, address all open spec issues
Review and define v1 of AMP data structures w/ “simple layout” description
Build X86 + Arm demo SW from hvac-demos
Build and run the ST A7 Linux + M4 Zephyr virtio-i2c demo on ST HW
Build the ST HW demo from the hvac-demo repo
Stretch: Rebase the Dual QEMU demo to the latest baseline and contain the shared memory usage to only the single IVISHMEM card
Stretch: Port the ST demo to a QEMU based platform, likely one of:
zynqmp A53+R5
QEMU m3 w/ ivshmem-flat and QEMU A53 w/ ivshmem
Highlights
Held Virtio-msg Sprint before Linaro Connect in Lisbon
Did multiple presentation and demos on virtio-msg at Linaro Connect
Lots of work on spec RFCv2 but not ready in May, new Target June 13
Issues
Progress was slow as Bill is out 2 weeks in May (1 week Connect and 1 week Vacation) and then was not 100% for 2 weeks more
Meeting May 8
No meeting: there were only four of us, we waited until 7 after the hour and did not get more
Move all topics to sprint
Sprint reminder
Call for Topics for today
Virtio-msg FF-A spec status
Sprint topics collection
Outstanding issues from Bill’s PR
What to call Device ID / Device number
Events and polling
Sprint May 13
Attendees: Bertrand, Edgar, Armelle, Viresh, Bill, Alex, Lina (as able), Lei (as able)
Agenda:
RFCv2
What to call Device ID / Device number
Final review from Bill’s PR
Events and polling
Explain the need for EVENT_CONFIG0, decide what to call it or delete it
Where to put details of messages: overview section or message definition
Combine DEVICE_ADDED and DEVICE_REMOVED to one EVENT_DEVICE with a state field?
What else to include: virtio 1.3 SHM, admin queues
When to send RFCv2
Aligned implementation plan
AMP data structure review and plan
FF-A foundation upstream status
FF-A spec status
Notes from the sprint are in this google doc