summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorLu Baolu <baolu.lu@linux.intel.com>2026-03-16 10:16:40 +0300
committerJoerg Roedel <joerg.roedel@amd.com>2026-03-17 15:20:06 +0300
commit39c20c4e83b9f78988541d829aa34668904e54a0 (patch)
treee51e2558fd448c7a0005d5084ad3927c458f9180 /include/linux
parentfe89277c9ceb0d6af0aa665bcf24a41d8b1b79cd (diff)
downloadlinux-39c20c4e83b9f78988541d829aa34668904e54a0.tar.xz
iommu/vt-d: Only handle IOPF for SVA when PRI is supported
In intel_svm_set_dev_pasid(), the driver unconditionally manages the IOPF handling during a domain transition. However, commit a86fb7717320 ("iommu/vt-d: Allow SVA with device-specific IOPF") introduced support for SVA on devices that handle page faults internally without utilizing the PCI PRI. On such devices, the IOMMU-side IOPF infrastructure is not required. Calling iopf_for_domain_replace() on these devices is incorrect and can lead to unexpected failures during PASID attachment or unwinding. Add a check for info->pri_supported to ensure that the IOPF queue logic is only invoked for devices that actually rely on the IOMMU's PRI-based fault handling. Fixes: 17fce9d2336d ("iommu/vt-d: Put iopf enablement in domain attach path") Cc: stable@vger.kernel.org Suggested-by: Kevin Tian <kevin.tian@intel.com> Reviewed-by: Kevin Tian <kevin.tian@intel.com> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com> Link: https://lore.kernel.org/r/20260310075520.295104-1-baolu.lu@linux.intel.com Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions