当前位置:首页 > 报告详情

Landing iommufd in Anolis-刘肄 薛帅.pdf

上传人: 表表 编号:1152819 2026-02-14 22页 2.24MB

1、Landing IOMMUFD to Anolis刘肄(Intel)薛帅(Alibaba)VFIO RecapIOMMUFDAnolis IOMMUFDstatusChallenge inPracticeVFIO RecapWhy would we need iommufdVFIO RecapVFIO A way to gain BareMetal I/O performance in virtualization A multi-layer userspace driver in Linuxvfio-pci Handle the device access like PCI configur

2、ation space r/w,BAR mmap,interrupts,etc.;Siblings:vfio-mdev,vfio-platform,etc;vfio_iommu_type1 driver Map/unmap the userspace memory in iommu I/O page table;Siblings:vfio_iommu_spapr_tce;UserspaceKernelHWvfio-pcivfio_iommu_type1VFIOVM/AppDeviceIOMMUVFIO RecapvDPA support vDPA has iommu map/unmap sup

3、port as well Not scale to support new IOMMU features(PASID,Nested translation etc)in two separate modules A central part is neededvfio user interface constraint for new features vfio provides group level isolation to user-not scale to extend to support PASID.vfio iommu interface is per vfio containe

4、r-not scale to support IOMMU features like Nested translationIOMMUFD IntroductionIOMMUFDiommufd is a new user interface for managing I/O page tables for devices managed by userspacedriversConsolidates all userspace iommu operations and interactions between userspace driver and kernel MAP/UNMAP,dirty

5、 tracking,PRI,PASID and nested translation etc.The single portal of supporting new IOMMU advancements for all userspace driver frameworksSimplified maintenance modelIOMMUFD SkeletonIOMMU FD Created per/dev/iommu opening Hold multiple I/O address spaces for the current process Support the iommu opera

6、tions(e.g.,DMA map/unmap)from userspaceIOAS An iommufd-local software handle representing an I/O address space Allocated via iommufd ioctlHWPT An iommufd-local software handle representing an I/O page table Allocated via iommufd ioctl or in attaching IOASkAPI interacting with VFIO Bind/unbind device

word格式文档无特别注明外均可编辑修改,预览文件经过压缩,下载原文更清晰!
三个皮匠报告文库所有资源均是客户上传分享,仅供网友学习交流,未经上传用户书面授权,请勿作商用。
1. **IOMMUFD定位**:作为统一I/O页表管理接口,替代VFIO,支持PASID、嵌套翻译等新特性,简化维护。 2. **核心挑战**: - P2P通信需支持设备MMIO内存映射,当前依赖dma-buf框架开发中。 - Stage-2内存钉扎耗时约390秒(1.6TB内存),影响VM启动效率。 - QEMU后端功能缺失(如IOMMU_VIOMMU_ALLOC),阻碍完整虚拟化栈部署。 3. **实践进展**: - Anolis已支持Intel QAT VF实时迁移(6.6.102-5),利用IOMMU硬件A/D位实现精确脏页跟踪。 - 嵌套翻译实验性支持(devel-6.6),硬件兼容性覆盖ARM/Intel/AMD/RISC-V。
**IOMMUFD优势?** **P2P如何实现?** **QAT迁移突破?**
客服
商务合作
小程序
服务号
折叠