aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorJean-Philippe Brucker <[email protected]>2020-03-26 10:35:58 +0100
committerJoerg Roedel <[email protected]>2020-03-27 11:10:20 +0100
commit39b3b3c9cac1b4a64a6e546c9faf0c1011d775d4 (patch)
treee2790d0c80b65e2c208e83e7ecd7406f53083c05 /tools/perf/scripts/python/export-to-sqlite.py
parent7062af3ed2ba451029e3733d9f677c68f5ea9e77 (diff)
iommu/virtio: Reject IOMMU page granule larger than PAGE_SIZE
We don't currently support IOMMUs with a page granule larger than the system page size. The IOVA allocator has a BUG_ON() in this case, and VFIO has a WARN_ON(). Removing these obstacles ranges doesn't seem possible without major changes to the DMA API and VFIO. Some callers of iommu_map(), for example, want to map multiple page-aligned regions adjacent to each others for scatter-gather purposes. Even in simple DMA API uses, a call to dma_map_page() would let the endpoint access neighbouring memory. And VFIO users cannot ensure that their virtual address buffer is physically contiguous at the IOMMU granule. Rather than triggering the IOVA BUG_ON() on mismatched page sizes, abort the vdomain finalise() with an error message. We could simply abort the viommu probe(), but an upcoming extension to virtio-iommu will allow setting different page masks for each endpoint. Reported-by: Bharat Bhushan <[email protected]> Signed-off-by: Jean-Philippe Brucker <[email protected]> Reviewed-by: Bharat Bhushan <[email protected]> Reviewed-by: Eric Auger <[email protected]> Reviewed-by: Robin Murphy <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Joerg Roedel <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions