diff options
author | Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com> | 2020-04-29 16:36:40 +0300 |
---|---|---|
committer | Joerg Roedel <jroedel@suse.de> | 2020-05-05 15:36:12 +0300 |
commit | 4cbf38511a007867def958872203ae8adb8e2351 (patch) | |
tree | eea8c33e8fcef1723f837208c81e9be570b9e20f /tools/perf/scripts/python/export-to-sqlite.py | |
parent | ff2a08b39bcede1b08d84d8b5c8ee1336a39c5df (diff) | |
download | linux-4cbf38511a007867def958872203ae8adb8e2351.tar.xz |
iommu: Add def_domain_type() callback in iommu_ops
Some devices are reqired to use a specific type (identity or dma)
of default domain when they are used with a vendor iommu. When the
system level default domain type is different from it, the vendor
iommu driver has to request a new default domain with
iommu_request_dma_domain_for_dev() and iommu_request_dm_for_dev()
in the add_dev() callback. Unfortunately, these two helpers only
work when the group hasn't been assigned to any other devices,
hence, some vendor iommu driver has to use a private domain if
it fails to request a new default one.
This adds def_domain_type() callback in the iommu_ops, so that
any special requirement of default domain for a device could be
aware by the iommu generic layer.
Signed-off-by: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
[ jroedel@suse.de: Added iommu_get_def_domain_type() function and use
it to allocate the default domain ]
Co-developed-by: Joerg Roedel <jroedel@suse.de>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
Link: https://lore.kernel.org/r/20200429133712.31431-3-joro@8bytes.org
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions