Re: [PATCH kernel v10 23/34] powerpc/iommu/powernv: Release replaced TCE

2015-05-15 Thread Thomas Huth
On Thu, 14 May 2015 13:53:57 +1000 Alexey Kardashevskiy wrote: > On 05/14/2015 01:00 AM, Thomas Huth wrote: > > On Tue, 12 May 2015 01:39:12 +1000 > > Alexey Kardashevskiy wrote: ... > >> -/* > >> - * hwaddr is a kernel virtual address here (0xc... bazillion), > >> - * tce_build converts it to a

Re: [PATCH kernel v10 23/34] powerpc/iommu/powernv: Release replaced TCE

2015-05-13 Thread Alexey Kardashevskiy
On 05/14/2015 01:00 AM, Thomas Huth wrote: On Tue, 12 May 2015 01:39:12 +1000 Alexey Kardashevskiy wrote: At the moment writing new TCE value to the IOMMU table fails with EBUSY if there is a valid entry already. However PAPR specification allows the guest to write new TCE value without cleari

Re: [PATCH kernel v10 23/34] powerpc/iommu/powernv: Release replaced TCE

2015-05-13 Thread Thomas Huth
On Tue, 12 May 2015 01:39:12 +1000 Alexey Kardashevskiy wrote: > At the moment writing new TCE value to the IOMMU table fails with EBUSY > if there is a valid entry already. However PAPR specification allows > the guest to write new TCE value without clearing it first. > > Another problem this p

[PATCH kernel v10 23/34] powerpc/iommu/powernv: Release replaced TCE

2015-05-11 Thread Alexey Kardashevskiy
At the moment writing new TCE value to the IOMMU table fails with EBUSY if there is a valid entry already. However PAPR specification allows the guest to write new TCE value without clearing it first. Another problem this patch is addressing is the use of pool locks for external IOMMU users such a