Re: [PATCH v4 03/21] powerpc/powernv: M64 support improvement

2015-05-10 Thread Gavin Shan
On Sat, May 09, 2015 at 08:24:14PM +1000, Alexey Kardashevskiy wrote: >On 05/01/2015 04:02 PM, Gavin Shan wrote: >>We're having the hardware or enforced (on P7IOC) limitation: M64 > >I would think if it is enforced, then it is enforced by hardware but you say >"hardware OR enforced" :) > PHB3 does

Re: [PATCH v4 03/21] powerpc/powernv: M64 support improvement

2015-05-09 Thread Alexey Kardashevskiy
On 05/01/2015 04:02 PM, Gavin Shan wrote: We're having the hardware or enforced (on P7IOC) limitation: M64 I would think if it is enforced, then it is enforced by hardware but you say "hardware OR enforced" :) segment#x can only be assigned to PE#x. IO and M32 segment can be mapped to arbi

[PATCH v4 03/21] powerpc/powernv: M64 support improvement

2015-04-30 Thread Gavin Shan
We're having the hardware or enforced (on P7IOC) limitation: M64 segment#x can only be assigned to PE#x. IO and M32 segment can be mapped to arbitrary PE# via IODT and M32DT. It means the PE number should be x if M64 segment#x has been assigned to the PE. Also, each PE own one M64 segment at most.