Re: [PATCH v8 16/18] vfio/type1: Allow transparent MSI IOVA allocation

2017-01-13 Thread Alex Williamson
On Wed, 11 Jan 2017 09:41:52 + Eric Auger wrote: > 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.

Re: [PATCH v8 16/18] vfio/type1: Allow transparent MSI IOVA allocation

2017-01-13 Thread Alex Williamson
On Wed, 11 Jan 2017 09:41:52 + Eric Auger wrote: > 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

[PATCH v8 16/18] vfio/type1: Allow transparent MSI IOVA allocation

2017-01-11 Thread Eric Auger
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

[PATCH v8 16/18] vfio/type1: Allow transparent MSI IOVA allocation

2017-01-11 Thread Eric Auger
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