summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorLogan Gunthorpe <logang@deltatee.com>2019-01-18 17:10:01 -0700
committerJon Mason <jdmason@kudzu.us>2019-02-11 09:26:30 -0500
commitc59666bb32b91da84b1d3df0e88789de9e827f61 (patch)
tree1899a86e550686291f178fca9ebccafbc70d99c5 /include
parent9143595a7e05a848384c240d34abcc4740a65897 (diff)
downloadlinux-0-day-c59666bb32b91da84b1d3df0e88789de9e827f61.tar.gz
linux-0-day-c59666bb32b91da84b1d3df0e88789de9e827f61.tar.xz
NTB: ntb_transport: Ensure the destination buffer is mapped for TX DMA
Presently, when ntb_transport is used with DMA and the IOMMU turned on, it fails with errors from the IOMMU such as: DMAR: DRHD: handling fault status reg 202 DMAR: [DMA Write] Request device [00:04.0] fault addr 381fc0340000 [fault reason 05] PTE Write access is not set This is because ntb_transport does not map the BAR space with the IOMMU. To fix this, we map the entire MW region for each QP after we assign the DMA channel. This prevents needing an extra DMA map in the fast path. Link: https://lore.kernel.org/linux-pci/499934e7-3734-1aee-37dd-b42a5d2a2608@intel.com/ Signed-off-by: Logan Gunthorpe <logang@deltatee.com> Reviewed-by: Dave Jiang <dave.jiang@intel.com> Signed-off-by: Jon Mason <jdmason@kudzu.us>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions