The userspace-api iommufd.rst has described it correctly but the uAPI doc was remained uncorrected. Thus, fix it.
Unified · Split
| @@ -995,7 +995,7 @@ struct iommu_viommu_alloc { · 994 unmodified lines | |||
| 995 | * @dev_id: The physical device to allocate a virtual instance on the vIOMMU | 995 | * @dev_id: The physical device to allocate a virtual instance on the vIOMMU |
| 996 | * @out_vdevice_id: Object handle for the vDevice. Pass to IOMMU_DESTORY | 996 | * @out_vdevice_id: Object handle for the vDevice. Pass to IOMMU_DESTORY |
| 997 | * @virt_id: Virtual device ID per vIOMMU, e.g. vSID of ARM SMMUv3, vDeviceID | 997 | * @virt_id: Virtual device ID per vIOMMU, e.g. vSID of ARM SMMUv3, vDeviceID |
| 998 | * of AMD IOMMU, and vRID of a nested Intel VT-d to a Context Table | 998 | * of AMD IOMMU, and vRID of Intel VT-d |
| 999 | * | 999 | * |
| 1000 | * Allocate a virtual device instance (for a physical device) against a vIOMMU. | 1000 | * Allocate a virtual device instance (for a physical device) against a vIOMMU. |
| 1001 | * This instance holds the device's information (related to its vIOMMU) in a VM. | 1001 | * This instance holds the device's information (related to its vIOMMU) in a VM. |