Re: [PATCH] powerpc/numa: Restrict possible nodes based on platform

2020-07-10 Thread Nathan Lynch
Srikar Dronamraju writes: > * Michael Ellerman [2020-07-07 15:02:17]: > >> Srikar Dronamraju writes: >> > $ lsprop /proc/device-tree/rtas/ibm,*associ*-domains >> > /proc/device-tree/rtas/ibm,current-associativity-domains >> > 0005 0001 0002 0002 0002 0010 >>

Re: [PATCH] powerpc/numa: Restrict possible nodes based on platform

2020-07-07 Thread Srikar Dronamraju
* Michael Ellerman [2020-07-07 15:02:17]: > Srikar Dronamraju writes: > > As per PAPR, there are 2 device tree property > > ibm,max-associativity-domains (which defines the maximum number of > > domains that the firmware i.e PowerVM can support) and > > ibm,current-associativity-domains (which

Re: [PATCH] powerpc/numa: Restrict possible nodes based on platform

2020-07-06 Thread Michael Ellerman
Srikar Dronamraju writes: > As per PAPR, there are 2 device tree property > ibm,max-associativity-domains (which defines the maximum number of > domains that the firmware i.e PowerVM can support) and > ibm,current-associativity-domains (which defines the maximum number of > domains that the

Re: [PATCH] powerpc/numa: Restrict possible nodes based on platform

2020-07-06 Thread Srikar Dronamraju
* Nathan Lynch [2020-07-06 19:44:31]: > Tyrel Datwyler writes: > >> --- a/arch/powerpc/mm/numa.c > >> +++ b/arch/powerpc/mm/numa.c > >> @@ -897,7 +897,7 @@ static void __init find_possible_nodes(void) > >>return; > >> > >>if (of_property_read_u32_index(rtas, > >> -

Re: [PATCH] powerpc/numa: Restrict possible nodes based on platform

2020-07-06 Thread Srikar Dronamraju
* Tyrel Datwyler [2020-07-06 13:58:42]: > On 7/5/20 11:40 PM, Srikar Dronamraju wrote: > > diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c > > index 9fcf2d195830..3d55cef1a2dc 100644 > > --- a/arch/powerpc/mm/numa.c > > +++ b/arch/powerpc/mm/numa.c > > @@ -897,7 +897,7 @@ static

Re: [PATCH] powerpc/numa: Restrict possible nodes based on platform

2020-07-06 Thread Nathan Lynch
Tyrel Datwyler writes: >> --- a/arch/powerpc/mm/numa.c >> +++ b/arch/powerpc/mm/numa.c >> @@ -897,7 +897,7 @@ static void __init find_possible_nodes(void) >> return; >> >> if (of_property_read_u32_index(rtas, >> -"ibm,max-associativity-domains", >> +

Re: [PATCH] powerpc/numa: Restrict possible nodes based on platform

2020-07-06 Thread Nathan Lynch
Srikar Dronamraju writes: > diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c > index 9fcf2d195830..3d55cef1a2dc 100644 > --- a/arch/powerpc/mm/numa.c > +++ b/arch/powerpc/mm/numa.c > @@ -897,7 +897,7 @@ static void __init find_possible_nodes(void) > return; > >

Re: [PATCH] powerpc/numa: Restrict possible nodes based on platform

2020-07-06 Thread Tyrel Datwyler
On 7/5/20 11:40 PM, Srikar Dronamraju wrote: > As per PAPR, there are 2 device tree property > ibm,max-associativity-domains (which defines the maximum number of > domains that the firmware i.e PowerVM can support) and > ibm,current-associativity-domains (which defines the maximum number of >

[PATCH] powerpc/numa: Restrict possible nodes based on platform

2020-07-06 Thread Srikar Dronamraju
As per PAPR, there are 2 device tree property ibm,max-associativity-domains (which defines the maximum number of domains that the firmware i.e PowerVM can support) and ibm,current-associativity-domains (which defines the maximum number of domains that the platform can support). Value of