Xen and the Art of Embedded Systems Virtualization
Talkat Embedded Linux Conference + OpenIoT Summit North America 2017 · on Thursday, 2017-02-23· at 16:30· Broadway III/IV·
summary
Xen on ARM uses hardware virtualization (no QEMU emulation) and implements the port in ~30,000 lines of code, claiming assign any MMIO region and interrupts to VMs and support for per-VM device trees. Demoed uses include running autopilot bare-metal alongside a Linux camera stack and an Android infotainment VM that boots in ~3s. Real-time tuning yields interrupt latencies under ~2 ms and features driver domains isolate flaky drivers so a bad wireless or GPU driver crashes a domain not the whole system.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 0:19Why do we need Xen
- 0:35Car hack example
- 2:32Drone example
- 5:02Efficiency in consolidation
- 6:03Xen
- 6:58Xen on the Cloud
- 7:48Embedded Roxanne
- 8:20Embedded requirements
- 13:21Virtualization Extensions
- 14:21Xen Features
- 16:44UI in Hardware
- 17:29Physical Interrupt
- 19:03Scheduler
- 19:22Realtime scheduler
- 20:37Memory introspection
- 22:05PV protocols
- 27:07Driver domains
- 28:51Global Logic Forum
- 30:03Now to Lose Some
- 30:41QNX neutrino VM
- 32:31Slides
- 34:21Security Process
- 36:35Release Schedule
- 37:53Device Tree
- 38:25PD Protocol
- 39:06Resources
- 40:21User Engagement
- 43:40GPU Specific Drivers
related talks
33mNext Generation Xen Architecture for Automotive
28mXen in OSS based In--Vehicle Infotainment Systems
38mBuilding Hard Real-Time Linux Systems with Xenomai
29mPerformance Optimization on Xen-based Android Device
26mXen based Automotive Reference Stack using Yocto
35mXen in Safety-Critical Systems
18mZVM: Zephyr-based Virtual Machine
40mZero-Overhead Virtualisation: It's a Trap!