linux-headers/linux/iommufd.h

15  * The ioctl interface follows a general format to allow for extensibility. Each
21  * ioctls use a standard meaning for common errnos:
78  * @out_ioas_id: Output IOAS ID for the allocated object
109  * @out_iova_alignment: Minimum alignment required for mapping IOVA
111  * Query an IOAS for ranges of allowed IOVAs. Mapping IOVA outside these ranges
120  * for mapping.
154  * Ensure a range of IOVAs are always available for allocation. If this call
179  * enum iommufd_ioas_map_flags - Flags for map and copy
224  * @flags: same as for iommu_ioas_map
225  * @ioas_id: same as for iommu_ioas_map
228  * @length: same as for iommu_ioas_map
229  * @iova: same as for iommu_ioas_map
306  *    PAGE_SIZE. This can be useful for benchmarking.  This is a per-IOAS
363  * @ioas_id: For IOMMU_VFIO_IOAS_SET the input IOAS ID to set
364  *           For IOMMU_VFIO_IOAS_GET will output the IOAS ID
384  * enum iommufd_hwpt_alloc_flags - Flags for HWPT allocation
387  * @IOMMU_HWPT_ALLOC_DIRTY_TRACKING: Dirty tracking support for device IOMMU is
396  *                          For the user that wants to attach PASID, ioas is
397  *                          not recommended for both the non-PASID part
441  * @ste: The first two double words of the user space Stream Table Entry for
473  * @dev_id: The device to allocate this HWPT for
489  * IOAS via the @pt_id. The @data_type for this allocation must be set to
490  * IOMMU_HWPT_DATA_NONE. The HWPT can be allocated as a parent HWPT for a
521  * enum iommu_hw_info_vtd_flags - Flags for VT-d hw_info
557  * @idr: Implemented features for ARM SMMU Non-secure programming interface
562  * For the details of @idr, @iidr and @aidr, please refer to the chapters
580  * important that VMMs do not read bits outside the list to allow for
582  * architecture are not currently supported by the kernel for nesting: HTTU,
608  * @IOMMU_HW_CAP_DIRTY_TRACKING: IOMMU hardware support for dirty tracking
674  * enum iommufd_hwpt_set_dirty_tracking_flags - Flags for steering dirty
701  * enum iommufd_hwpt_get_dirty_bitmap_flags - Flags for getting dirty bits
729  * Walk the IOMMU pagetables for a given IOVA range to return a bitmap
749  * @IOMMU_HWPT_INVALIDATE_DATA_VTD_S1: Invalidation data for VTD_S1
750  * @IOMMU_VIOMMU_INVALIDATE_DATA_ARM_SMMUV3: Invalidation data for ARM SMMUv3
758  * enum iommu_hwpt_vtd_s1_invalidate_flags - Flags for Intel VT-d
777  * The Intel VT-d specific invalidation data for user-managed stage-1 cache
818  * @hwpt_id: ID of a nested HWPT or a vIOMMU, for cache invalidation
829  * Invalidate iommu cache for user-managed page table or vIOMMU. Modifications
853  * enum iommu_hwpt_pgfault_flags - flags for struct iommu_hwpt_pgfault
864  * enum iommu_hwpt_pgfault_perm - perm bits for struct iommu_hwpt_pgfault
865  * @IOMMU_PGFAULT_PERM_READ: request for read permission
866  * @IOMMU_PGFAULT_PERM_WRITE: request for write permission
889  * @length: a hint of how much data the requestor is expecting to fetch. For
952  * @IOMMU_VIOMMU_TYPE_DEFAULT: Reserved for future use
967  * @out_viommu_id: Output virtual IOMMU ID for the allocated object
973  * - Security namespace for guest owned ID, e.g. guest-controlled cache tags
996  * @out_vdevice_id: Object handle for the vDevice. Pass to IOMMU_DESTORY
1000  * Allocate a virtual device instance (for a physical device) against a vIOMMU.
1017  * This transfers pinned memory counts for every memory map in every IOAS
1022  * This API is useful for transferring operation of a device from one process
1034  * enum iommu_veventq_flag - flag for struct iommufd_vevent_header
1042  * struct iommufd_vevent_header - Virtual Event Header for a vEVENTQ Status
1076  * @IOMMU_VEVENTQ_TYPE_DEFAULT: Reserved for future use
1098  * StreamID field reports a virtual device ID. To receive a virtual event for a
1117  * Explicitly allocate a virtual event queue interface for a vIOMMU. A vIOMMU
1118  * can have multiple FDs for different types, but is confined to one per @type.