diff options
| author |  Srikar Dronamraju <srikar@linux.vnet.ibm.com>
| 2020-07-24 16:28:09 +0530 |
|---|---|---|
| committer |  Michael Ellerman <mpe@ellerman.id.au>
| 2020-07-26 23:34:25 +1000 |
| commit | dbce456280857f329af9069af5e48a9b6ebad146 (patch) | |
| tree | fdb5a776e7cbae7c5de828b8e687c345983e39b1 /arch/powerpc/lib/locks.c | |
| parent | macintosh/via-macii: Clarify definition of macii_init() (diff) | |
| download | linux-dbce456280857f329af9069af5e48a9b6ebad146.tar.gz linux-dbce456280857f329af9069af5e48a9b6ebad146.tar.bz2 linux-dbce456280857f329af9069af5e48a9b6ebad146.zip | |
powerpc/numa: Limit possible nodes to within num_possible_nodes
MAX_NUMNODES is a theoretical maximum number of nodes thats is
supported by the kernel. Device tree properties exposes the number of
possible nodes on the current platform. The kernel would detected this
and would use it for most of its resource allocations. If the platform
now increases the nodes to over what was already exposed, then it may
lead to inconsistencies. Hence limit it to the already exposed nodes.
Suggested-by: Nathan Lynch <nathanl@linux.ibm.com>
Signed-off-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20200724105809.24733-1-srikar@linux.vnet.ibm.com
Diffstat (limited to 'arch/powerpc/lib/locks.c')
0 files changed, 0 insertions, 0 deletions