Documentation/userspace-api/iommufd.rst

35 - IOMMUFD_OBJ_IOAS, representing an I/O address space (IOAS), allowing map/unmap
39   container it copies an IOVA map to a list of iommu_domains held within it.
41 - IOMMUFD_OBJ_DEVICE, representing a device that is bound to iommufd by an
44 - IOMMUFD_OBJ_HW_PAGETABLE, representing an actual hardware I/O page table
85 1. IOMMUFD_OBJ_IOAS is created via the IOMMU_IOAS_ALLOC uAPI. An iommufd can
90 2. IOMMUFD_OBJ_DEVICE is created when an external driver calls the IOMMUFD kAPI
91    to bind a device to an iommufd. The driver is expected to implement a set of
97 3. IOMMUFD_OBJ_HW_PAGETABLE is created when an external driver calls the IOMMUFD
98    kAPI to attach a bound device to an IOAS. Similarly the external driver uAPI
110       Future IOMMUFD updates will provide an API to create and manipulate the
113 A device can only bind to an iommufd due to DMA ownership claim and attach to at
127 - Automatic domain - refers to an iommu domain created automatically when
128   attaching a device to an IOAS object. This is compatible to the semantics of
131 - Manual domain - refers to an iommu domain designated by the user as the
137   IOMMUFD access interface to access the IOAS. This starts by creating an
140   page * lists, or doing direct read/write to an IOVA.
153 ultimately derived from userspace VAs via an mm_struct. Once they have been
154 pinned the PFNs are stored in IOPTEs of an iommu_domain or inside the pinned_pfns
155 xarray if they have been pinned through an iommufd_access.
161 An io_pagetable is composed of iopt_areas pointing at iopt_pages, along with a
181 device-centric uAPI for connecting its device to an iommufd, instead of
198 /dev/iommufd or extending VFIO to SET_CONTAINER using an iommufd instead of a