This page will be updated during the month and is not final until after the 1st week of December.
Summary of Month
Plans
Prototype a kernel level driver for ivshmem that can exchange messages with QEMU’s virtio-msg-ivshmem mode
Highlights
Issues/Changes
WIP Presentations
(Intro slides on front page of project were updated)
Meeting notes October 10th
Follow up on mailing list virtio-msg@lists.linaro.org
Any issues?
Making the working spec available to all
Bertrand has published host first darft of the markdown format to the list
Can we host this markdown format in git somewhere? (w/ images etc)
Can we publish a snapshot of the PDF on the HVAC home page util another form is ready?
Updates from Bill
Updates from Edgar?
Updates from Lei?
Updates from others?
Actions:
Meeting notes October 24th
Notice: no meeting on Nov 7th
Updates from Bill
I have a kernel that can send a GET_STATUS msg to Edgar’s QEMU on another machine and receive the response.
Next steps: deferred RX processing and hooking to Viresh’s virtio-msg common code
Note: this code is ugly and prototype quality, Edgar and I need to agree on common shared memory format that will remove hard-coded values
Corresponding system level code is here. Each of these branches (kernel and demo) will be rebased as I go along.
Note: This will be the first time we interoperate between Authors. So far we have tested Edgar to Edgar and Viresh to Viresh
Updates from Edgar?
Updates from Lei?
Updates from Viresh:
Updated ffa driver Lei started, added memory sharing interface
Starting work on the interface to FFA DMA hal, tring to make it generic
Lorenzo may have some patches to integrate FFA indirect message support in the kernel
Starting to work with Bertrand’s Xen work which should allow to do any DOM to any DOM (including DOMU to DOMU)
No API for getting FFA messages to user space (needed on device side)
Need to discuss in Dublin
Discuss meeting timings, its getting very late for India (22:30 IST) from Nov, possible to move it two hours earlier ?
Updates from Armelle
Virtio-msg and OPTEE? Joakim/Sumit: need to discuss in Dublin
OPTEE as VM
Keep SOC vendor in real TZ
Allow SW provider to use OPTEE in a pKVM VM
[Joakim, Something about secure timer → Armelle uses protected storage for this, timer only needs slow update (10s)]
HW Crypto keeps track of key expiration
Does OPTEE support TA’s in Rust, Joakim: yes the basics are there. As you use it for real work, more may be needed
Updates from others?