aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/linux/iommu.h
diff options
context:
space:
mode:
authorRobin Murphy <robin.murphy@arm.com>2017-01-19 20:57:46 +0000
committerWill Deacon <will.deacon@arm.com>2017-01-23 11:48:16 +0000
commitfdbe574eb69312a7fbe09674d69c01b80e4ed9dc (patch)
tree6c4cc7dd1fe4eb0188343281fb83572383ddb8dd /include/linux/iommu.h
parentLinux 4.10-rc3 (diff)
downloadwireguard-linux-fdbe574eb69312a7fbe09674d69c01b80e4ed9dc.tar.xz
wireguard-linux-fdbe574eb69312a7fbe09674d69c01b80e4ed9dc.zip
iommu/dma: Allow MSI-only cookies
IOMMU domain users such as VFIO face a similar problem to DMA API ops with regard to mapping MSI messages in systems where the MSI write is subject to IOMMU translation. With the relevant infrastructure now in place for managed DMA domains, it's actually really simple for other users to piggyback off that and reap the benefits without giving up their own IOVA management, and without having to reinvent their own wheel in the MSI layer. Allow such users to opt into automatic MSI remapping by dedicating a region of their IOVA space to a managed cookie, and extend the mapping routine to implement a trivial linear allocator in such cases, to avoid the needless overhead of a full-blown IOVA domain. Signed-off-by: Robin Murphy <robin.murphy@arm.com> Reviewed-by: Tomasz Nowicki <tomasz.nowicki@caviumnetworks.com> Reviewed-by: Eric Auger <eric.auger@redhat.com> Tested-by: Eric Auger <eric.auger@redhat.com> Tested-by: Tomasz Nowicki <tomasz.nowicki@caviumnetworks.com> Tested-by: Bharat Bhushan <bharat.bhushan@nxp.com> Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'include/linux/iommu.h')
0 files changed, 0 insertions, 0 deletions