vfio/type1: Allow transparent MSI IOVA allocation
authorEric Auger <eric.auger@redhat.com>
Thu, 19 Jan 2017 20:58:01 +0000 (20:58 +0000)
committerWill Deacon <will.deacon@arm.com>
Mon, 23 Jan 2017 15:00:46 +0000 (15:00 +0000)
commit5d704992189fe8683a23f583a2f4f137a9b9d28b
treeff14d4ac48f55b725a82e25255fce329ad18bb8e
parent59768527db3de41afb0586e677e322012e6a392b
vfio/type1: Allow transparent MSI IOVA allocation

When attaching a group to the container, check the group's
reserved regions and test whether the IOMMU translates MSI
transactions. If yes, we initialize an IOVA allocator through
the iommu_get_msi_cookie API. This will allow the MSI IOVAs
to be transparently allocated on MSI controller's compose().

Signed-off-by: Eric Auger <eric.auger@redhat.com>
Acked-by: Alex Williamson <alex.williamson@redhat.com>
Reviewed-by: Tomasz Nowicki <tomasz.nowicki@caviumnetworks.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>
drivers/vfio/vfio_iommu_type1.c