Confidential Devices (TEE I/O): A series of modest proposals
summary
Phase one lands in 6.19 with PCI, VFIO, DMABUF and IOMMUFD pieces merged and the repo shows 75% complete for the host stack, but KVM integration and the guest lock/accept flow remain unfinished. Work focuses on mapping private MMIO and private DMA into KVM, getting DMABUF to convey MMIO private/shared metadata, resolving DMABUF lifetime and PFN vs page issues, and aligning MMUFD interfaces across architectures before attestation and deployment.
AI-written summary · about
chapters (17)
- 0:00Introduction to TIO
- 1:05Problem statement and platform support
- 3:12Phase one: PCI layer changes
- 4:15Phase two: Guest side support
- 5:21Phase three: Host side setup
- 10:19Private MMIO and KVM coordination
- 12:47Private DMA and DMA buffers
- 14:57MMU FD and architecture alignment
- 16:24Maturity map and consensus tracking
- 17:28Dynamic device locking workflow
- 21:03DMA streaming and substream IDs
- 22:50Driver rebinding challenges
- 24:13Attestation and user space helpers
- 25:15PCI PASID support
- 26:17Host side flow and TSM details
- 27:01Attestation differences from CMA
- 27:23How to get involved
related talks
31mSecure IO
39miommufd discussion
25mExploring I/O Support for Virtualization-Based Trusted Execution Environment
42mProtecting the Linux Kernel from Confidential Computing Threats in Virtual Environments
20mIntel Virtualization Technology Extensions to Enable Hardware Isolated VMs
36mEverybody is talking about Confidential Computing - the minimum Devs should know
16mOpening the I/O gates with confidential containers
50mProtected KVM on Arm64: A Technical Deep Dive