iommu/arm-smmu-v3: Do not allow a SVA domain to be set on the wrong PASID

Browse source

The SVA code is wired to assume that the SVA is programmed onto the
mm->pasid. The current core code always does this, so it is fine.

Add a check for clarity.

Tested-by: Nicolin Chen <nicolinc@nvidia.com>
Tested-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Link: https://lore.kernel.org/r/3-v6-228e7adf25eb+4155-smmuv3_newapi_p2_jgg@nvidia.com
Signed-off-by: Will Deacon <will@kernel.org>

...

This commit is contained in:

Jason Gunthorpe 2024-03-27 15:07:49 -03:00 • committed by Will Deacon

parent 734554fdfc

commit fdc69d39e7

1 changed files with 3 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

3

drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c

View file