Re: [RFC v3 09/10] iommu/arm-smmu: Implement reserved region get/put callbacks

2016-12-07 Thread Auger Eric
Hi Robin, On 07/12/2016 19:24, Robin Murphy wrote: > On 07/12/16 15:02, Auger Eric wrote: >> Hi Robin, >> On 06/12/2016 19:55, Robin Murphy wrote: >>> On 15/11/16 13:09, Eric Auger wrote: The get() populates the list with the PCI host bridge windows and the MSI IOVA range. At

Re: [RFC v3 09/10] iommu/arm-smmu: Implement reserved region get/put callbacks

2016-12-07 Thread Robin Murphy
On 07/12/16 15:02, Auger Eric wrote: > Hi Robin, > On 06/12/2016 19:55, Robin Murphy wrote: >> On 15/11/16 13:09, Eric Auger wrote: >>> The get() populates the list with the PCI host bridge windows >>> and the MSI IOVA range. >>> >>> At the moment an arbitray MSI IOVA window is set at 0x800

Re: [RFC v3 09/10] iommu/arm-smmu: Implement reserved region get/put callbacks

2016-12-07 Thread Auger Eric
Hi Robin, On 06/12/2016 19:55, Robin Murphy wrote: > On 15/11/16 13:09, Eric Auger wrote: >> The get() populates the list with the PCI host bridge windows >> and the MSI IOVA range. >> >> At the moment an arbitray MSI IOVA window is set at 0x800 >> of size 1MB. This will allow to report those

Re: [RFC v3 09/10] iommu/arm-smmu: Implement reserved region get/put callbacks

2016-12-06 Thread Robin Murphy
On 15/11/16 13:09, Eric Auger wrote: > The get() populates the list with the PCI host bridge windows > and the MSI IOVA range. > > At the moment an arbitray MSI IOVA window is set at 0x800 > of size 1MB. This will allow to report those info in iommu-group > sysfs? > > Signed-off-by: Eric

[RFC v3 09/10] iommu/arm-smmu: Implement reserved region get/put callbacks

2016-11-15 Thread Eric Auger
The get() populates the list with the PCI host bridge windows and the MSI IOVA range. At the moment an arbitray MSI IOVA window is set at 0x800 of size 1MB. This will allow to report those info in iommu-group sysfs? Signed-off-by: Eric Auger --- RFC v2 -> v3: - use