summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorNicolin Chen <nicolinc@nvidia.com>2026-09-15 09:38:14 -0700
committerWill Deacon <will@kernel.org>2026-10-04 16:01:29 +0000
commit580bbfcdcd2e2be5e29e19acbe4be44da9be2837 (patch)
tree4142bc418072419b23964533ad63bd7876cac6d5 /scripts
parentab0dbf411aced59c04ce86fd8443faf13bdc9936 (diff)
downloadlinux-580bbfcdcd2e2be5e29e19acbe4be44da9be2837.tar.gz
linux-580bbfcdcd2e2be5e29e19acbe4be44da9be2837.zip
iommu/arm-smmu-v3: Add arm_smmu_attach_release()
The IOPF teardown is done in arm_smmu_remove_master_domain() when releasing the master_domain on detach, under the global arm_smmu_asid_lock mutex. A later change will add an IOPF workqueue flush to that teardown, which can block on a user-faulting page-fault handler. Holding the arm_smmu_asid_lock across it would stall every unrelated attachment in the system. Split the teardown out of arm_smmu_remove_master_domain(), to a new helper arm_smmu_attach_release() that runs after arm_smmu_asid_lock is released. No functional change: the old master_domain belongs to no other device, so freeing it outside the lock stays safe, still under iommu_group->mutex. Reviewed-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com> Signed-off-by: Nicolin Chen <nicolinc@nvidia.com> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions