diff options
author | Lu Baolu <baolu.lu@linux.intel.com> | 2023-08-18 13:10:30 +0300 |
---|---|---|
committer | Jason Gunthorpe <jgg@nvidia.com> | 2023-08-18 18:52:15 +0300 |
commit | 60fedb262bbc632ab58bfdec7f6e47b2f94992d3 (patch) | |
tree | 2c3558924afcd2d96d7731093d19d51fe23b0563 /drivers/iommu/iommufd/main.c | |
parent | 92766e1b953d6e419684b39f55dab574287dd144 (diff) | |
download | linux-60fedb262bbc632ab58bfdec7f6e47b2f94992d3.tar.xz |
iommu: Add new iommu op to get iommu hardware information
Introduce a new iommu op to get the IOMMU hardware capabilities for
iommufd. This information will be used by any vIOMMU driver which is owned
by userspace.
This op chooses to make the special parameters opaque to the core. This
suits the current usage model where accessing any of the IOMMU device
special parameters does require a userspace driver that matches the kernel
driver. If a need for common parameters, implemented similarly by several
drivers, arises then there's room in the design to grow a generic
parameter set as well. No wrapper API is added as it is supposed to be
used by iommufd only.
Different IOMMU hardware would have different hardware information. So the
information reported differs as well. To let the external user understand
the difference, enum iommu_hw_info_type is defined. For the iommu drivers
that are capable to report hardware information, it should have a unique
iommu_hw_info_type and return to caller. For the driver doesn't report
hardware information, caller just uses IOMMU_HW_INFO_TYPE_NONE if a type
is required.
Link: https://lore.kernel.org/r/20230818101033.4100-3-yi.l.liu@intel.com
Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Co-developed-by: Nicolin Chen <nicolinc@nvidia.com>
Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
Signed-off-by: Yi Liu <yi.l.liu@intel.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'drivers/iommu/iommufd/main.c')
0 files changed, 0 insertions, 0 deletions