IOMMUFD Discussion
summary
Project exposes full IOMMU features to user space via an iommufd API that aims to replace vfio internals, add passive device support and nested translation, and let user space choose dirty‑tracking policy. A device-specific tracker API and an io mmu ownership model are merged; about 168 patches merged so far. Nested translation exists as a proof‑of‑concept and is roughly 95% compatible with current vfio behavior; target upstream inclusion is aimed around Linux 6.2 while performance and some edge compatibility remain unresolved.
AI-written summary · about
chapters (10)
- 0:00Introduction to IOMMUFD
- 1:33Core features and goals
- 3:44Architectural transition
- 5:25API design and integration
- 7:19Status update and progress
- 10:03Platform and model support
- 11:53Compatibility and challenges
- 14:54Q&A: Groups and security
- 19:06Q&A: Tracking and usage
- 23:34Nested translation and wrap-up
related talks
30miommu page table consolidation and iommufd
24mA Virtual IOMMU With Cooperative DMA Buffer Tracking
22mAMD-vIOMMU: A Hardware-assisted Virtual IOMMU Technology
27mVFIO User - Using VFIO as the IPC Protocol in Multi-process QEMU
19mlibvfio-user: Status Update
16mUnifying KVM API for protected VM and utilities
55mSecure IO BoF
36mShared Virtual Addressing for High Performance Arm Infrastructure Platforms