2025-03 Update and Notes
This page will be updated during the month and is not final until after the 1st week of April.
Summary of Month
Plans
Work toward the 2nd spec RFC, address all open spec issues
Demo x86 + Arm virtio-net over PCIe at Embedded World
Build X86 + Arm demo SW from hvac-demos
Build and run the ST A7 Linux + M4 Zephyr virtio-i2c demo on ST HW
Define and share AMP data structures w/ “simple layout” description
Stretch: Rebase the Dual QEMU demo to the latest baseline and contain the shared memory usage to only the single IVISHMEM card
Stretch: Build the ST HW demo from the hvac-demo repo
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
Demoed x86 + Arm virtio-net over PCIe on AMD hardware at Embedded World
Progress on the virtio-msg spec toward an RFCv2
Progress toward building the AMD hardware from hvac-demo repo, but it is not done yet.
Issues
Bill will be out 1 week for Embedded World
Meeting March 13
No meeting as Bill was at Embedded World
Meeting Notes March 27
Viresh:
New work: get notifications for each virt-queue.
blocked today on pKVM for memory mapping (see email thread on pKVM on list). This relates to memory sharing Guest to Trusty w/o host being able to see.
VSOCK from Linux to Trusty, tested by google
Viresh tested himself Host to Trusty, low level setup & memory sharing
Bill asked Viresh to sync his Xen VM to VM demo to the current spec
Bertrand said to wait until next week so we can land the below changes
Spec sync, things to look at: message numbers, messages are not variable size (but fixed per bus instance) error message,
Common Data structures:
Goal is to use for AMP but also for:
FFA when not using FFA message APIs (using shared memory and notifications)
Xen native (shared memory and Xen events)
Bill pseudo header: hvac-demo/notes/amp-data-structures.h at wip-amp-data-defs · wmamills/hvac-demo
Arnuads:
Version numbers
Do what IBM channel transport does
We don’t want version per device
Version at bus level makes sense
Bus tells device level the protocol version and max message size when it creates the device instance
Error numbers
We should align to the error defs defined for Admin Queues
Leave moving or renaming these defs for upstream alignment