iommu/vtd: Per device dma ops
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | iommu/vt-d: Refactor find_domain() helperdrivers/ | +20 | 4 replies | |
| 2/3 | iommu/vt-d: Apply per-device dma_opsdrivers/ | +10 | 3 replies | |
| 3/3 | iommu/vt-d: Cleanup after using per-device dma opsdrivers/ | +5 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] iommu/vtd: Per device dma ops
Current Intel IOMMU driver sets the system level dma_ops. This means every dma API call will be routed to the iommu driver, even the privileged user might select to bypass iommu for some specific devices.
Furthermore, if the priviledged user requests to bypass iommu translation for a device, the iommu driver might fall back to use dma domain blindly if the device is not able to address all system memory.
This sets the per-device dma_ops only if a device is using DMA domain. Otherwise, use the default dma_ops for direct dma.
Lu Baolu (3):
iommu/vt-d: Refactor find_domain() helper iommu/vt-d: Apply per-device dma_ops iommu/vt-d: Cleanup after using per-device dma ops
drivers/iommu/intel-iommu.c | 131 ++++++++++-------------------------- 1 file changed, 34 insertions(+), 97 deletions(-)
Signature · 1 line
2.17.1