Documentation/userspace-api/iommu.rst

1 .. SPDX-License-Identifier: GPL-2.0
23 supported user-kernel APIs are as follows:
25 1. Bind/Unbind guest PASID (e.g. Intel VT-d)
35 1. Emulated and para-virtualised vIOMMUs
36 2. Multiple vendors (Intel VT-d, ARM SMMU, etc.)
41 Although the data structures defined in IOMMU UAPI are self-contained,
45 Extension Rules & Precautions
46 -----------------------------
50 1. Adding new fields by re-purposing the padding[] field. No size change.
70 ----------------------
71 When IOMMU UAPI extension results in some structure size increase,
83 ----------------
98 IOMMU vendor driver should report the below features to IOMMU UAPI
108 VFIO kernel code shall query IOMMU vendor driver for the support of
111 Documentation/driver-api/vfio.rst.
115 ------------------------------
121 In this tight-knit VFIO-IOMMU interface, the ultimate consumer of the
122 IOMMU UAPI data is the host IOMMU driver. VFIO facilitates user-kernel
170 - Generic IOMMU layer checks argsz range based on UAPI data in the
173 - Generic IOMMU layer checks content of the UAPI data for non-zero
178 - Vendor IOMMU driver checks argsz based on vendor flags. UAPI data
179   is consumed based on flags. Vendor driver has access to
180   unadulterated argsz value in case of vendor specific future
183   where there's vendor data outside of the structure definition.
187 - structure contains vendor data
190 - structure contains only generic data
195 Sharing UAPI with in-kernel users
196 ---------------------------------
197 For UAPIs that are shared with in-kernel users, a wrapper function is
206 In-kernel caller ::