Re: [PATCH v9 07/26] powerpc/powernv: Fix initial IO and M32 segmap

2016-05-04 Thread Alexey Kardashevskiy
On 05/03/2016 03:41 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

Re: [PATCH v9 07/26] powerpc/powernv: Fix initial IO and M32 segmap

2016-05-03 Thread Gavin Shan
On Wed, May 04, 2016 at 01:31:04PM +1000, Alistair Popple wrote: >On Tue, 3 May 2016 15:41:26 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 v9 07/26] powerpc/powernv: Fix initial IO and M32 segmap

2016-05-03 Thread Alistair Popple
On Tue, 3 May 2016 15:41:26 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

[PATCH v9 07/26] powerpc/powernv: Fix initial IO and M32 segmap

2016-05-02 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