diff options
author | Jason Gunthorpe <jgg@nvidia.com> | 2024-06-25 15:37:33 +0300 |
---|---|---|
committer | Will Deacon <will@kernel.org> | 2024-07-02 17:39:47 +0300 |
commit | 85f2fb6ef4137c631c9d2663716d998d7e4f164f (patch) | |
tree | 158df0018355ea88ba827967ff4fd3414148a686 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 678d79b98028ce2365b30e35479bea0e555c23d3 (diff) | |
download | linux-85f2fb6ef4137c631c9d2663716d998d7e4f164f.tar.xz |
iommu/arm-smmu-v3: Start building a generic PASID layer
Add arm_smmu_set_pasid()/arm_smmu_remove_pasid() which are to be used by
callers that already constructed the arm_smmu_cd they wish to program.
These functions will encapsulate the shared logic to setup a CD entry that
will be shared by SVA and S1 domain cases.
Prior fixes had already moved most of this logic up into
__arm_smmu_sva_bind(), move it to it's final home.
Following patches will relieve some of the remaining SVA restrictions:
- The RID domain is a S1 domain and has already setup the STE to point to
the CD table
- The programmed PASID is the mm_get_enqcmd_pasid()
- Nothing changes while SVA is running (sva_enable)
SVA invalidation will still iterate over the S1 domain's master list,
later patches will resolve that.
Tested-by: Nicolin Chen <nicolinc@nvidia.com>
Tested-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
Reviewed-by: Jerry Snitselaar <jsnitsel@redhat.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Link: https://lore.kernel.org/r/2-v9-5cd718286059+79186-smmuv3_newapi_p2b_jgg@nvidia.com
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions