diff options
| author | Nicolin Chen <nicolinc@nvidia.com> | 2025-10-22 19:21:07 -0700 |
|---|---|---|
| committer | Joerg Roedel <joerg.roedel@amd.com> | 2025-10-27 13:55:35 +0100 |
| commit | c21b34762e2f4a9a255b4ef69a018f8787699bf8 (patch) | |
| tree | 9fb803ef14a5d3668b3ae3e13d2a60d978058ff9 | |
| parent | 680a6a60fc0846cb0364201f7625700da1e8ffa1 (diff) | |
iommu/amd: Set release_domain to blocked_domain
The set_dev_pasid for a release domain never gets called anyhow. So, there
is no point in defining a separate release_domain from the blocked_domain.
Simply reuse the blocked_domain.
Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
| -rw-r--r-- | drivers/iommu/amd/iommu.c | 10 |
1 files changed, 1 insertions, 9 deletions
diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c index 2e1865daa1ce..6f4559eb5121 100644 --- a/drivers/iommu/amd/iommu.c +++ b/drivers/iommu/amd/iommu.c @@ -2685,14 +2685,6 @@ void amd_iommu_init_identity_domain(void) protection_domain_init(&identity_domain); } -/* Same as blocked domain except it supports only ops->attach_dev() */ -static struct iommu_domain release_domain = { - .type = IOMMU_DOMAIN_BLOCKED, - .ops = &(const struct iommu_domain_ops) { - .attach_dev = blocked_domain_attach_device, - } -}; - static int amd_iommu_attach_device(struct iommu_domain *dom, struct device *dev) { @@ -3042,7 +3034,7 @@ static const struct iommu_dirty_ops amd_dirty_ops = { const struct iommu_ops amd_iommu_ops = { .capable = amd_iommu_capable, .blocked_domain = &blocked_domain, - .release_domain = &release_domain, + .release_domain = &blocked_domain, .identity_domain = &identity_domain.domain, .domain_alloc_paging_flags = amd_iommu_domain_alloc_paging_flags, .domain_alloc_sva = amd_iommu_domain_alloc_sva, |