| Age | Commit message (Collapse) | Author |
|---|
|
This was removed in kernel a9ee6cf (5.14 onwards).
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
A user reported getting NUMA warnings like the ones reported here:
https://www.suse.com/support/kb/doc/?id=000021040
"Fail to get numa node for CPU:0 bus:0 dev:0 fn:1"
...and repeated for every core on the platform. Distracting.
When I asked if it was a crazy big server system with multiple CPU
sockets and localized RAM near each socket - the answer was "no".
Turns out they didn't choose NUMA support - rather we did it for them.
Yocto has been and still remains more "embedded leaning". That is not
to say we can't support NUMA. We just shouldn't be enabling it by
default in the base x86-64 config fragment that everyone uses.
Move the two NUMA settings that were not in our existing numa.cfg
feature out of the BSP and into the feature.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Remove obsolete NODES_SPAN_OTHER_NODES kernel option which was
removed from kernel starting with v5.7.0, commit acd3f5c441e9
("mm: remove early_pfn_in_nid() and CONFIG_NODES_SPAN_OTHER_NODES").
Signed-off-by: Daniel Dragomir <Daniel.Dragomir@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Yann CARDAILLAC <ycnakajsph@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
When added, this feature enables NUMA support
Signed-off-by: Syed Johan Arif Bin Syed Mohamad Fauzi <syed.johan.arif.syed.mohamad.fauzi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
Ross Burton
Paul Gortmaker
Daniel Dragomir
Yann CARDAILLAC
Syed Johan Arif Bin Syed Mohamad Fauzi