Re: [PATCH v8 08/45] powerpc/powernv: Fix initial IO and M32 segmap

2016-04-13 Thread Alexey Kardashevskiy
On 04/13/2016 05:53 PM, Gavin Shan wrote: On Wed, Apr 13, 2016 at 04:21:07PM +1000, Alexey Kardashevskiy wrote: On 02/17/2016 02:43 PM, Gavin Shan wrote: There are two arrays for IO and M32 segment maps on every PHB. The index of the arrays are segment number and the value stored in the

Re: [PATCH v8 08/45] powerpc/powernv: Fix initial IO and M32 segmap

2016-04-13 Thread Gavin Shan
On Wed, Apr 13, 2016 at 04:21:07PM +1000, Alexey Kardashevskiy wrote: >On 02/17/2016 02:43 PM, Gavin Shan wrote: >>There are two arrays for IO and M32 segment maps on every PHB. >>The index of the arrays are segment number and the value stored >>in the corresponding element is PE number,

Re: [PATCH v8 08/45] powerpc/powernv: Fix initial IO and M32 segmap

2016-04-13 Thread Alexey Kardashevskiy
On 02/17/2016 02:43 PM, Gavin Shan wrote: There are two arrays for IO and M32 segment maps on every PHB. The index of the arrays are segment number and the value stored in the corresponding element is PE number, indicating the segment is assigned to the PE. Initially, all elements in those two

[PATCH v8 08/45] powerpc/powernv: Fix initial IO and M32 segmap

2016-02-16 Thread Gavin Shan
There are two arrays for IO and M32 segment maps on every PHB. The index of the arrays are segment number and the value stored in the corresponding element is PE number, indicating the segment is assigned to the PE. Initially, all elements in those two arrays are zeroes, meaning all segments are