+ Oleksandr Tyshchenko
-- Artem ________________________________ From: Alex Bennée alex.bennee@linaro.org Sent: Wednesday, July 13, 2022 6:39:23 PM To: Trilok Soni tsoni@quicinc.com Cc: Stratos Mailing List stratos-dev@op-lists.linaro.org; Viresh Kumar viresh.kumar@linaro.org; Mathieu Poirier mathieu.poirier@linaro.org; Mike Holmes mike.holmes@linaro.org; Azzedine Touzni atouzni@qti.qualcomm.com; Stefano Stabellini stefano.stabellini@xilinx.com; Christopher Clark christopher.w.clark@gmail.com; Arnd Bergmann arnd.bergmann@linaro.org; Peter Griffin peter.griffin@linaro.org; AKASHI Takahiro takahiro.akashi@linaro.org; Artem Mygaiev Artem_Mygaiev@epam.com; Leonardo Garcia leonardo.garcia@linaro.org; Randy Linnell randy.linnell@linaro.org; don.harbin@linaro.org don.harbin@linaro.org; Sumit Semwal sumit.semwal@linaro.org; xen-devel@lists.xenproject.org xen-devel@lists.xenproject.org; Wei Liu wl@xen.org; Florescu, Andreea fandree@amazon.com; rust-vmm@lists.opendev.org rust-vmm@lists.opendev.org Subject: Add Xen support to vmm-reference? (was Re: Call for topics and skipping next weeks sync)
(added xen/rust-vmm to CC)
Trilok Soni tsoni@quicinc.com writes:
Hello Alex,
It would be good to check if there is a enough interest to make "vmm-reference" extended to work w/ Type-1 Hypervisor like Xen. This will clean-up vmm-reference w/ KVM references, and it will be a good independent tool to test the new interfaces additions in the rust-vmm.
https://urldefense.com/v3/__https://github.com/rust-vmm/vmm-reference__%3B%2... [github[.]com]
We have certainly talked about it before and the we've put in some of the groundwork with the xen-sys crate (https://urldefense.com/v3/__https://github.com/rust-vmm/xen-sys__%3B%21%21GF... [github[.]com]) which we are using for the xen-vhost-master work. Off the top of my head we would need to work out:
- Which additional APIs need implementing for VMM lifecycle management - How the run loop would look - AIUI Hyper-V munges this for rust-vmm by providing a KVM-like ioctl API (POC via CrosVM: https://urldefense.com/v3/__https://github.com/petrutlucian94/crosvm/tree/wi... [github[.]com]) - See also https://urldefense.com/v3/__https://github.com/rust-vmm/community/issues/121... [github[.]com] - Would we aim for full independence from the exiting Xen userspace libs? - xen-vhost-master was brought up using them, now slowly being replaced with pure rust
I've added it as a discussion topic for the sync call:
https://urldefense.com/v3/__https://calendar.google.com/event?action=TEMPLAT... [calendar[.]google[.]com]
It would be great is we could get any interested folks from the rust-vmm and Xen communities to come along to the call.
---Trilok Soni
-----Original Message----- From: Alex Bennée alex.bennee@linaro.org Sent: Wednesday, July 13, 2022 2:16 AM To: Stratos Mailing List stratos-dev@op-lists.linaro.org Cc: Viresh Kumar viresh.kumar@linaro.org; Mathieu Poirier mathieu.poirier@linaro.org; Mike Holmes mike.holmes@linaro.org; Azzedine Touzni atouzni@qti.qualcomm.com; Stefano Stabellini stefano.stabellini@xilinx.com; Christopher Clark christopher.w.clark@gmail.com; Arnd Bergmann arnd.bergmann@linaro.org; Peter Griffin peter.griffin@linaro.org; AKASHI Takahiro takahiro.akashi@linaro.org; Artem Mygaiev Artem_Mygaiev@epam.com; Leonardo Garcia leonardo.garcia@linaro.org; Trilok Soni tsoni@quicinc.com; Randy Linnell randy.linnell@linaro.org; don.harbin@linaro.org; Sumit Semwal sumit.semwal@linaro.org Subject: Call for topics and skipping next weeks sync
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi All,
I'll be on holiday (moving house) next week so I won't be able to chair the Stratos sync meeting. As it is the middle of summer I'm going to propose we skip next weeks sync and re-convene on the 3rd of August. Any objections?
While on the subject of sync meetings are there any topics to discuss. We've had some discussions on next rust-vmm device to implement but beyond a vague "maybe virtio-gpu to help with demos" I don't think we've nailed it down. virtio-can also keeps getting mentioned and while useful I'm wary it's not pushing our exploration of the possibilities of virtio further.
I did a talk at GST22 last week which was an overview of VirtIO and what we had done so far as well as discussing some future directions. You can see the talk at:
https://urldefense.com/v3/__https://huawei-events.de/en/gsts22-j83dco-vod.ht... [huawei-events[.]de] (Day 2 stream, Chapter 6/TS 05:13:00)
In it potential future areas of exploration where:
Improve Xen API ═══════════════
• More standard mmap • direct irqfd/eventfd routing
Memory Isolation ════════════════
• fat virtqueue • iommu/grants vs regions (x-over with pKVM/CCA?)
Bare metal rust ═══════════════
• re-use exiting VirtIO logic • but without POSIX layer
I'd like to get a better steer on what we should focus on next after we've demoed our existing rust-vmm daemons and the Xen vhost-master work.
-- Alex Bennée