summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorViktor Kleen <viktor@kleen.org>2026-02-05 16:49:41 +0800
committerJoerg Roedel <joerg.roedel@amd.com>2026-02-06 11:01:00 +0100
commit02f9d76a76adb5ea16b4e3b403496c42033f8fd1 (patch)
treeb5b407a519373509f63a47673131986b2ded212a /include
parent18f7fcd5e69a04df57b563360b88be72471d6b62 (diff)
iommu/vt-d: Treat PAGE_SNOOP and PWSNP separately
The PASID_FLAG_PAGE_SNOOP and PASID_FLAG_PWSNP constants are identical. This will cause the pasid code to always set both or neither of the PGSNP and PWSNP bits in PASID table entries. However, PWSNP is a reserved bit if SMPWC is not set in the IOMMU's extended capability register, even if SC is supported. This has resulted in DMAR errors when testing the iommufd code on an Arrow Lake platform. With this patch, those errors disappear and the PASID table entries look correct. Fixes: 101a2854110fa ("iommu/vt-d: Follow PT_FEAT_DMA_INCOHERENT into the PASID entry") Cc: stable@vger.kernel.org Signed-off-by: Viktor Kleen <viktor@kleen.org> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> Link: https://lore.kernel.org/r/20260202192109.1665799-1-viktor@kleen.org Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com> Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions