Skip to content

iommu/vt-d: Consolidate various cache flush ops

Lu Baolu linux-iommu lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest5 patches 8 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5iommu/vt-d: Extend iommu_flush for scalable modedrivers/iommu/dmar.c drivers/iommu/intel-iommu.c include/linux/intel-iommu.h+98 -920 replies
2/5iommu/vt-d: Consolidate pasid cache invalidationdrivers/iommu/intel-iommu.c drivers/iommu/intel-pasid.c include/linux/intel-iommu.h+18 -160 replies
3/5iommu/vt-d: Consolidate device tlb invalidationdrivers/iommu/dmar.c drivers/iommu/intel-iommu.c drivers/iommu/intel-pasid.c +1 more+31 -280 replies
4/5iommu/vt-d: Consolidate pasid-based tlb invalidationdrivers/iommu/intel-iommu.c drivers/iommu/intel-pasid.c drivers/iommu/intel-svm.c+48 -361 reply
5/5iommu/vt-d: Consolidate pasid-based device tlb invalidationdrivers/iommu/intel-iommu.c drivers/iommu/intel-svm.c+47 -270 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/5] iommu/vt-d: Consolidate various cache flush ops

Intel VT-d 3.0 introduces more caches and interfaces for software to flush when it runs in the scalable mode. Currently various cache flush helpers are scattered around. This consolidates them by putting them in the existing iommu_flush structure.

/* struct iommu_flush - Intel IOMMU cache invalidation ops
*
* @cc_inv: invalidate context cache
* @iotlb_inv: Invalidate IOTLB and paging structure caches when software
* has changed second-level tables.
* @p_iotlb_inv: Invalidate IOTLB and paging structure caches when software
* has changed first-level tables.
* @pc_inv: invalidate pasid cache
* @dev_tlb_inv: invalidate cached mappings used by requests-without-PASID
* from the Device-TLB on a endpoint device.
* @p_dev_tlb_inv: invalidate cached mappings used by requests-with-PASID
* from the Device-TLB on an endpoint device
*/

struct iommu_flush {
        void (*cc_inv)(struct intel_iommu *iommu, u16 did,
                       u16 sid, u8 fm, u64 type);
        void (*iotlb_inv)(struct intel_iommu *iommu, u16 did, u64 addr,
                          unsigned int size_order, u64 type);
        void (*p_iotlb_inv)(struct intel_iommu *iommu, u16 did, u32 pasid,
                            u64 addr, unsigned long npages, bool ih);
        void (*pc_inv)(struct intel_iommu *iommu, u16 did, u32 pasid,
                       u64 granu);
        void (*dev_tlb_inv)(struct intel_iommu *iommu, u16 sid, u16 pfsid,
                            u16 qdep, u64 addr, unsigned int mask);
        void (*p_dev_tlb_inv)(struct intel_iommu *iommu, u16 sid, u16 pfsid,
                              u32 pasid, u16 qdep, u64 addr,
                              unsigned long npages);
};

The name of each cache flush ops is defined according to the spec section 6.5 so that people are easy to look up them in the spec.

Best regards,
Lu Baolu

Lu Baolu (5):
iommu/vt-d: Extend iommu_flush for scalable mode iommu/vt-d: Consolidate pasid cache invalidation iommu/vt-d: Consolidate device tlb invalidation iommu/vt-d: Consolidate pasid-based tlb invalidation iommu/vt-d: Consolidate pasid-based device tlb invalidation

 drivers/iommu/dmar.c        |  61 ---------
 drivers/iommu/intel-iommu.c | 246 +++++++++++++++++++++++++++++-------
 drivers/iommu/intel-pasid.c |  39 +-----
 drivers/iommu/intel-svm.c   |  60 ++-------
 include/linux/intel-iommu.h |  39 ++++--
 5 files changed, 244 insertions(+), 201 deletions(-)
Signature · 1 line
2.17.1