Re: [PATCH v2 3/3] spapr_numa.c: fix ibm,max-associativity-domains calculation

2021-01-28 Thread David Gibson
On Thu, Jan 28, 2021 at 02:42:13PM -0300, Daniel Henrique Barboza wrote: > The current logic for calculating 'maxdomain' making it a sum of > numa_state->num_nodes with spapr->gpu_numa_id. spapr->gpu_numa_id is > used as a index to determine the next available NUMA id that a > given NVGPU can use.

Re: [PATCH v2 3/3] spapr_numa.c: fix ibm,max-associativity-domains calculation

2021-01-28 Thread Greg Kurz
On Thu, 28 Jan 2021 14:42:13 -0300 Daniel Henrique Barboza wrote: > The current logic for calculating 'maxdomain' making it a sum of > numa_state->num_nodes with spapr->gpu_numa_id. spapr->gpu_numa_id is > used as a index to determine the next available NUMA id that a > given NVGPU can use. > >

[PATCH v2 3/3] spapr_numa.c: fix ibm, max-associativity-domains calculation

2021-01-28 Thread Daniel Henrique Barboza
The current logic for calculating 'maxdomain' making it a sum of numa_state->num_nodes with spapr->gpu_numa_id. spapr->gpu_numa_id is used as a index to determine the next available NUMA id that a given NVGPU can use. The problem is that the initial value of gpu_numa_id, for any topology that has