Re: [PATCH v9 4/7] vfio: allow reserved msi iova registration

2016-05-10 Thread Eric Auger
Hi Alex, On 05/10/2016 05:29 PM, Alex Williamson wrote: > On Wed, 4 May 2016 11:54:15 + > Eric Auger wrote: > >> The user is allowed to register a reserved MSI IOVA range by using the >> DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA. >>

Re: [PATCH v9 4/7] vfio: allow reserved msi iova registration

2016-05-10 Thread Alex Williamson
On Wed, 4 May 2016 11:54:15 + Eric Auger wrote: > The user is allowed to register a reserved MSI IOVA range by using the > DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA. > This region is stored in the vfio_dma rb tree. At that point the

Re: [PATCH v9 4/7] vfio: allow reserved msi iova registration

2016-05-09 Thread Eric Auger
Hi Chalamarla, On 05/05/2016 09:22 PM, Chalamarla, Tirumalesh wrote: > > > > > > On 5/4/16, 4:54 AM, "linux-arm-kernel on behalf of Eric Auger" > eric.au...@linaro.org> wrote: > >> The user is allowed to register a reserved MSI

[PATCH v9 4/7] vfio: allow reserved msi iova registration

2016-05-04 Thread Eric Auger
The user is allowed to register a reserved MSI IOVA range by using the DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA. This region is stored in the vfio_dma rb tree. At that point the iova range is not mapped to any target address yet. The host kernel will use those iova