Re: [PATCH v6 2/5] vfio: allow the user to register reserved iova range for MSI mapping

2016-04-08 Thread Eric Auger
Hi Alex, On 04/08/2016 06:41 PM, Alex Williamson wrote: > On Fri, 8 Apr 2016 17:48:01 +0200 > Eric Auger wrote: > > Hi Eric, > >> Hi Alex, >> On 04/07/2016 08:29 PM, Alex Williamson wrote: >>> On Thu, 7 Apr 2016 15:43:29 +0200 >>> Eric Auger wrote: >>> Hi Alex, On 04/07/2016 12:07

Re: [PATCH v6 2/5] vfio: allow the user to register reserved iova range for MSI mapping

2016-04-08 Thread Alex Williamson
On Fri, 8 Apr 2016 17:48:01 +0200 Eric Auger wrote: Hi Eric, > Hi Alex, > On 04/07/2016 08:29 PM, Alex Williamson wrote: > > On Thu, 7 Apr 2016 15:43:29 +0200 > > Eric Auger wrote: > > > >> Hi Alex, > >> On 04/07/2016 12:07 AM, Alex Williamson wrote: > >>> On Mon, 4 Apr 2016 08:30:08 +000

Re: [PATCH v6 2/5] vfio: allow the user to register reserved iova range for MSI mapping

2016-04-08 Thread Eric Auger
Hi Alex, On 04/07/2016 08:29 PM, Alex Williamson wrote: > On Thu, 7 Apr 2016 15:43:29 +0200 > Eric Auger wrote: > >> Hi Alex, >> On 04/07/2016 12:07 AM, Alex Williamson wrote: >>> On Mon, 4 Apr 2016 08:30:08 + >>> Eric Auger wrote: >>> The user is allowed to [un]register a reserved

Re: [PATCH v6 2/5] vfio: allow the user to register reserved iova range for MSI mapping

2016-04-07 Thread Alex Williamson
On Thu, 7 Apr 2016 15:43:29 +0200 Eric Auger wrote: > Hi Alex, > On 04/07/2016 12:07 AM, Alex Williamson wrote: > > On Mon, 4 Apr 2016 08:30:08 + > > Eric Auger wrote: > > > >> The user is allowed to [un]register a reserved IOVA range by using the > >> DMA MAP API and setting the new fla

Re: [PATCH v6 2/5] vfio: allow the user to register reserved iova range for MSI mapping

2016-04-07 Thread Eric Auger
Hi Alex, On 04/07/2016 12:07 AM, Alex Williamson wrote: > On Mon, 4 Apr 2016 08:30:08 + > Eric Auger wrote: > >> The user is allowed to [un]register a reserved IOVA range by using the >> DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA. >> It provides the base addres

Re: [PATCH v6 2/5] vfio: allow the user to register reserved iova range for MSI mapping

2016-04-06 Thread Alex Williamson
On Mon, 4 Apr 2016 08:30:08 + Eric Auger wrote: > The user is allowed to [un]register a reserved IOVA range by using the > DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA. > It provides the base address and the size. This region is stored in the > vfio_dma rb tree.

Re: [PATCH v6 2/5] vfio: allow the user to register reserved iova range for MSI mapping

2016-04-04 Thread Eric Auger
On 04/04/2016 11:30 AM, kbuild test robot wrote: > Hi Eric, > > [auto build test ERROR on iommu/next] > [also build test ERROR on v4.6-rc2 next-20160404] > [if your patch is applied to the wrong git tree, please drop us a note to > help improving the system] > > url: > https://github.com/0da

Re: [PATCH v6 2/5] vfio: allow the user to register reserved iova range for MSI mapping

2016-04-04 Thread kbuild test robot
Hi Eric, [auto build test ERROR on iommu/next] [also build test ERROR on v4.6-rc2 next-20160404] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Eric-Auger/KVM-PCIe-MSI-passthrough-on-ARM-ARM64

[PATCH v6 2/5] vfio: allow the user to register reserved iova range for MSI mapping

2016-04-04 Thread Eric Auger
The user is allowed to [un]register a reserved IOVA range by using the DMA MAP API and setting the new flag: VFIO_DMA_MAP_FLAG_MSI_RESERVED_IOVA. It provides the base address and the size. This region is stored in the vfio_dma rb tree. At that point the iova range is not mapped to any target addres