Re: [PATCH v4 04/21] powerpc/powernv: Improve IO and M32 mapping

2015-05-10 Thread Gavin Shan
On Sat, May 09, 2015 at 08:53:38PM +1000, Alexey Kardashevskiy wrote: >On 05/01/2015 04:02 PM, Gavin Shan wrote: >>The PHB's IO or M32 window is divided evenly to segments, each of >>them can be mapped to arbitrary PE# by IODT or M32DT. Current code >>figures out the consumed IO and M32 segments by

Re: [PATCH v4 04/21] powerpc/powernv: Improve IO and M32 mapping

2015-05-09 Thread Alexey Kardashevskiy
On 05/01/2015 04:02 PM, Gavin Shan wrote: The PHB's IO or M32 window is divided evenly to segments, each of them can be mapped to arbitrary PE# by IODT or M32DT. Current code figures out the consumed IO and M32 segments by one particular PE from the windows of the PE's upstream bridge. It won't b

[PATCH v4 04/21] powerpc/powernv: Improve IO and M32 mapping

2015-04-30 Thread Gavin Shan
The PHB's IO or M32 window is divided evenly to segments, each of them can be mapped to arbitrary PE# by IODT or M32DT. Current code figures out the consumed IO and M32 segments by one particular PE from the windows of the PE's upstream bridge. It won't be reliable once we extend M64 windows of roo