IOMMU user API header was introduced to support nested DMA translation and related fault handling. The current UAPI data structures consist of three areas that cover the interactions between host kernel and guest: - fault handling - cache invalidation - bind guest page tables, i.e. guest PASID
Future extensions are likely to support more architectures and vIOMMU features. In the previous discussion, using user-filled data size and feature flags is made a preferred approach over a unified version number. https://lkml.org/lkml/2020/1/29/45 In addition to introduce argsz field to data structures, this patchset is also trying to document the UAPI design, usage, and extension rules. VT-d driver changes to utilize the new argsz field is included, VFIO usage is to follow. Thanks, Jacob Changeog: v2: - Removed unified API version and helper - Introduced argsz for each UAPI data - Introduced UAPI doc Jacob Pan (3): docs: IOMMU user API iommu/uapi: Add argsz for user filled data iommu/vt-d: Sanity check uapi argsz filled by users Documentation/userspace-api/iommu.rst | 210 ++++++++++++++++++++++++++++++++++ drivers/iommu/intel-iommu.c | 16 +++ drivers/iommu/intel-svm.c | 12 ++ include/uapi/linux/iommu.h | 6 + 4 files changed, 244 insertions(+) create mode 100644 Documentation/userspace-api/iommu.rst -- 2.7.4