Virtio-msg: Making Virtio Work Where It Does Not Today
summary
A new transport called virtio‑msg converts MMIO reads and writes to messages so virtio works on AMP cores, secure world TEEs, and devices that cannot trap+emulate; it keeps v‑rings, virtqueues and buffers unchanged and adds bus layers for DMA, discovery and out‑of‑band notifications. Work includes spec, kernel, QEMU, Rust‑VMM, Zephyr/RTOS libraries and containerized demos using Podman/Docker; demos show Zephyr M4 I2C bridging and an AMD PCI card demo reaching 2 Gbit with QEMU + hardware demos available to run.
AI-written summary · about
chapters (12)
- 0:00Virtio and Virtio-msg intro
- 2:55Virtio-msg changes
- 4:22Virtio-msg use cases
- 7:16Virtio-msg in secure/normal worlds
- 8:58Virtio-msg x86-ARM
- 10:22Why Virtio-msg with hypervisor
- 12:36Virtio-msg transport architecture
- 14:42Bus-level Virtio-msg
- 18:54Memory models in Virtio-msg
- 24:19Virtio-msg status and demos
- 28:11Running Virtio-msg demo
- 30:41Q&A performance and usage
related talks
37mHypervisor-less virtio for Real-time and Safety
26mVirtio-Loopback Status and Next Steps
45mTrust, confidentiality, and hardening: the virtio lessons
38mVirtio-loopback: The AGL Hardware Abstraction Layer for Non-Virtualized Environme...
33mZephyr‑Based VIRTIO Backend on Xen: Toward Open Source Functional Safety
35mVirtio-Loopback: An Hardware Abstraction Layer (HAL) for Non-Virtualized Environm...
36mShared Virtual Addressing for High Performance Arm Infrastructure Platforms
30mEnabling a Software-Defined Automotive Edge with VirtIO Based Device Virtua...