Skip to end of banner
Go to start of banner

2024-09 Update and Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

WIP Presentations

(node yet)

Meeting notes Sept 12

  • New attendees in the invite list

    • Sangshetty Patil (AMD San Jose, monitoring)

    • Sean Keys (Android Auto all things Virtulization)

  • Bill has started a Demo and CI project for all the individual demos

    • https://github.com/wmamills/hvac-demo

    • Viresh’s kernel demo is there and works with 100% automation

    • The project builds everything and can run it

    • Bill is in the process of adding Edgar’s demos from here

    • Happy to rename the project if we want to broaden the scope to all of virtio-msg but need owners for the write up of each demo to be added. (Like Viresh and Edgar did).

    • Plan to enable this as CI

  • Bertrand published his work in Xen for FFA indirect message support

    • Needs kernel work to match but right now no one is available from Linaro

    • Arm is working on kernel side FFA v1.2 target kernel v6.12

    • Working to bring Xen up to FFA v1.2

  • We have created the mailing list virtio-msg@lists.linaro.org

  • Updates from Edgar

    • Xen mediated virtio-proxy?

      • proxy is in xen hypervisor (not public (yet))

      • qemu is doing foreign memory maps and xen events for notification

      • Trying to do something that works with current kernels

    • What is this message-queue thing? It is Gaunha hypervisor specific message passing

  • Updates from Lei?

    • Getting ready to take Google’s Trusty Virtio-msg VSOCK drop

    • Using Viresh’s base

  • Armelle’s updates

    • Trusty drop

      • will be QEMU based drop

      • Will be switching to virtio-msg / FFA

      • The Rust dependecies were a struggle to integrate into TEE environment

    • microDroid VM Update

      • Linux frontend and backend w/ virtio-msg-ffa VM to VM

      • Backend is microDroid w/ RustVMM devices

      • CrossVM

        • Google’s RustVMM based VMM

      • End goal is to have VM to VM

    • What about header files for the messages

      • Desire to dual license the Linux header file at least to start

  • Edgar

    • Spec updates: disable queues, and others.

    • Need to be able to shutdown and bring back up

    • Cleanup & restart after abortive shutdown of either side

    • Graceful shutdown initiated from the device (like eject button on CD)

    • Should we be giving a heads-up to the upstream virtio spec owners?

Actions:

  • No labels