The existing SVA and IOPF implementation assumes that devices report I/O page faults via PCI PRI. This is not always true as some emerging devices are designed to handle the I/O page faults by themselves without ever sending PCI page requests nor advertising PRI capability. Refactor the SVA and IOPF code to allow SVA support with IOPF handled either by IOMMU (PCI PRI) or device driver (device-specific IOPF). This series is based on v6.3-rc1 and also available at github: https://github.com/LuBaolu/intel-iommu/commits/intel-iommu-refactor-iopf-v3 Change log: v3: - Split removing unnecessary checks in iopf disabling path into a separate patch. - Add some in-line comments. v2: - https://lore.kernel.org/linux-iommu/20230309025639.26109-1-baolu.lu@xxxxxxxxxxxxxxx/ - Separate a fix patch and merge it into v6. 3-rc1 [commit 60b1daa3b168 ("iommu/vt-d: Fix error handling in sva enable/disable paths")] - Disallow device-specific IOPF is device advertising PRI capability; - Add some extra patches to move all IOPF related code to the IOPF enabling/disabling paths. v1: Initial post - https://lore.kernel.org/linux-iommu/20230203084456.469641-1-baolu.lu@xxxxxxxxxxxxxxx/ Lu Baolu (6): dmaengine: idxd: Add enable/disable device IOPF feature iommu/vt-d: Allow SVA with device-specific IOPF iommu/vt-d: Move iopf code from SVA to IOPF enabling path iommu/vt-d: Move pfsid and ats_qdep calculation to device probe path iommu/vt-d: Move PRI handling to IOPF feature path iommu/vt-d: Remove unnecessary checks in iopf disabling path drivers/dma/idxd/init.c | 31 +++++++-- drivers/iommu/intel/iommu.c | 132 ++++++++++++++++++++++++------------ 2 files changed, 112 insertions(+), 51 deletions(-) -- 2.34.1
