summaryrefslogtreecommitdiff
path: root/arch/s390/lib/mem.S
diff options
context:
space:
mode:
authorMartin Schwidefsky <schwidefsky@de.ibm.com>2018-07-31 17:14:18 +0300
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2018-08-01 08:48:33 +0300
commitfb7d7518b0d65955f91c7b875c36eae7694c69bd (patch)
treededff29ea5e0555417a8d786686eeed70d301b59 /arch/s390/lib/mem.S
parent8cce437fbb5c1f2af2f63834fa05082596beca5d (diff)
downloadlinux-fb7d7518b0d65955f91c7b875c36eae7694c69bd.tar.xz
s390/numa: move initial setup of node_to_cpumask_map
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 051f3ca02e46432c0965e8948f00c07d8a2f09c0 "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>
Diffstat (limited to 'arch/s390/lib/mem.S')
0 files changed, 0 insertions, 0 deletions