Implement SMMU passthrough using the default domain
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 5 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 5 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] Implement SMMU passthrough using the default domain
Quoted 27 lines · Rob Clark
Quoted 13 lines · Joerg Roedel
Quoted 11 lines · Sricharan
Thanks for this series. We had a case with the GPU.
The GPU's iommu was setup by kernel and the GPU
also does dynamic updates for on-the-fly switching between process pagetables. GPU driver was not using DMA domain and the GPU's firmware was always expecting to run out of contextbank
'0' (although not correct) , which was not the case after the DMA domain
was made default as '0' was getting allocated for DMA domain and there were concerns about reusing the DMA domain as well.
Now with this series, looks there is an way out of that that can be tried.So should the default domain not be per device specific selectable ?
Quoted 7 lines
Note that iommu-drivers can request direct-mapping for any given device on its initializtion. This is used on x86 for devices that need a 1-1 mapping for some reason.
Also device drivers can use the iommu-api and assign their own domain to a device, which allows them to manage the dma address space on their own.
Part of the problem is that
dev->archdata.dma_opsgets wired up toiommu_dma_ops. Which isn't so bad on it's own, except that cache ops are not exposed to drivers, forcing us to use dma-mapping API (dma_map_sg, etc) for cache operations.
Quoted 5 lines
Possibly we should just expose cache op's to drivers bypass this abuse of dma-mapping.
btw, Will, we definitely want this to *not* rely on kcmdline for the gpu with it's own private iommu case..
I still need to understand the unmanaged domain case, but I don't really see why that's related to this series to be honest.
Will