remarkable-linux/arch/s390/numa
Martin Schwidefsky 2ac8fbd174 s390/numa: move initial setup of node_to_cpumask_map
commit fb7d7518b0 upstream.

The numa_init_early initcall sets the node_to_cpumask_map[0] to the
full cpu_possible_mask. Unfortunately this early_initcall is too late,
the NUMA setup for numa=emu is done even earlier. The order of calls
is numa_setup() -> emu_update_cpu_topology(), then the early_initcalls(),
followed by sched_init_domains().

Starting with git commit 051f3ca02e
"sched/topology: Introduce NUMA identity node sched domain"
the incorrect node_to_cpumask_map[0] really screws up the domain
setup and the kernel panics with the follow oops:

Cc: <stable@vger.kernel.org> # v4.15+
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-09-05 09:26:40 +02:00
..
Makefile
mode_emu.c
numa.c s390/numa: move initial setup of node_to_cpumask_map 2018-09-05 09:26:40 +02:00
numa_mode.h
toptree.c
toptree.h