This page will be updated during the month and is not final until after the 1st week of May.

Summary of Month

Do a 2nd spec RFC, address all open spec issues
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
Rebase the Dual QEMU demo to the latest baseline and contain the shared memory usage to only the single IVISHMEM card
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

Issues

We are still planning to have this meeting but many people will be on vacation this week
Alex, Edgar, Manos, Arnaud, Dan, Sumit, Lei
Edgar: for QEMU, after connect plan to sync with spec and can make a clean rebase branch at that time
Side bar on functional saftey WRT xen
Also maybe update to Viresh’s /dev/virtio-msgN to send & receive messages
Alex: what is the QEMU interface for what we have now on Sapphire VPR hw?
- Edgar: uio module
  - get IRQ
  - map memory uncached to userspace (Window to x86
Bill asked Viresh & Alex how memory mapping works in rust vhost-user
- Alex: the frontend process configres details about ranges and methods to the device process at device startup time and then the device process does the operations as needed
  - Right now the devices bin files are built with support for Xen OR kvm but the goal is to have one bin file that can do both based on what the hypervisor specific process tells it to
- Details: VHOST_USER_PROTOCOL_F_XEN_MMAP vhost-user feature and the :xen mmap flags: in https://qemu.readthedocs.io/en/master/interop/vhost-user.html#
Virtio-msg sprint status
- Confirmed for Tuesday before Connect (May 13)
- Confirmed: Edgar, Bertrand, Bill, Alex, Viresh, Lei
- Invited but declined: Arnaud & Dan
- Invited but not confirmed: Armelle and others from Google