Re: [PATCH kernel] powerpc/powernv/ioda: Store correct amount of memory used for table

2019-02-12 Thread Alexey Kardashevskiy
On 12/02/2019 18:33, Alexey Kardashevskiy wrote: > > > On 12/02/2019 11:20, David Gibson wrote: >> On Mon, Feb 11, 2019 at 06:48:01PM +1100, Alexey Kardashevskiy wrote: >>> We store 2 multilevel tables in iommu_table - one for the hardware and >>> one with the corresponding userspace addresses

Re: [PATCH kernel] powerpc/powernv/ioda: Store correct amount of memory used for table

2019-02-11 Thread Alexey Kardashevskiy
On 12/02/2019 11:20, David Gibson wrote: > On Mon, Feb 11, 2019 at 06:48:01PM +1100, Alexey Kardashevskiy wrote: >> We store 2 multilevel tables in iommu_table - one for the hardware and >> one with the corresponding userspace addresses. Before allocating >> the tables, the iommu_table_group_ops

Re: [PATCH kernel] powerpc/powernv/ioda: Store correct amount of memory used for table

2019-02-11 Thread David Gibson
On Mon, Feb 11, 2019 at 06:48:01PM +1100, Alexey Kardashevskiy wrote: > We store 2 multilevel tables in iommu_table - one for the hardware and > one with the corresponding userspace addresses. Before allocating > the tables, the iommu_table_group_ops::get_table_size() hook returns > the combined si

[PATCH kernel] powerpc/powernv/ioda: Store correct amount of memory used for table

2019-02-10 Thread Alexey Kardashevskiy
We store 2 multilevel tables in iommu_table - one for the hardware and one with the corresponding userspace addresses. Before allocating the tables, the iommu_table_group_ops::get_table_size() hook returns the combined size of the two and VFIO SPAPR TCE IOMMU driver adjusts the locked_vm counter co