[PW_SID:1149727] iommu/riscv: Report cache coherency capability - #2511
[PW_SID:1149727] iommu/riscv: Report cache coherency capability#2511linux-riscv-bot wants to merge 1 commit into
Conversation
VFIO and iommufd require IOMMU_CAP_CACHE_COHERENCY because they use IOMMU_CACHE mappings and have no userspace cache-maintenance path. RISC-V page tables preserve physical memory attributes for IOMMU_CACHE mappings. Svpbmt marks mappings without IOMMU_CACHE as non-cacheable, but preserving physical attributes cannot make a noncoherent device path coherent. Report the capability only for devices marked DMA coherent. This limits userspace assignment to paths that can honor cacheable mappings. Signed-off-by: Andrew Jones <andrew.jones@oss.qualcomm.com> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
|
Patch 1: "iommu/riscv: Report cache coherency capability" |
2 participants
PR for series 1149727 applied to workflow__riscv__fixes
Name: iommu/riscv: Report cache coherency capability
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=1149727
Version: 1