-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NUMA: Early use of cpu_to_node() returns 0 instead of the correct node id #492
Conversation
Upstream branch: e5075d8 |
Upstream branch: 3a6dd5f |
00805dc
to
0f9eb38
Compare
Upstream branch: 3a6dd5f |
0f9eb38
to
2324c95
Compare
Upstream branch: e2d6b54 |
2324c95
to
ef60fde
Compare
Upstream branch: e2d6b54 |
ef60fde
to
10d2e76
Compare
Upstream branch: cb4ede9 |
10d2e76
to
1b27466
Compare
Upstream branch: cb4ede9 |
1b27466
to
43927d9
Compare
86689b1
to
43a5b17
Compare
…e id During the kernel booting, the generic cpu_to_node() is called too early in arm64, powerpc and riscv when CONFIG_NUMA is enabled. There are at least four places in the common code where the generic cpu_to_node() is called before it is initialized: 1.) early_trace_init() in kernel/trace/trace.c 2.) sched_init() in kernel/sched/core.c 3.) init_sched_fair_class() in kernel/sched/fair.c 4.) workqueue_init_early() in kernel/workqueue.c In order to fix the bug, the patch introduces early_numa_node_init() which is called after smp_prepare_boot_cpu() in start_kernel. early_numa_node_init will initialize the "numa_node" as soon as the early_cpu_to_node() is ready, before the cpu_to_node() is called at the first time. Signed-off-by: Huang Shijie <shijie@os.amperecomputing.com> Signed-off-by: Björn Töpel <bjorn@rivosinc.com>
Upstream branch: 45e0b0f |
43927d9
to
ed81346
Compare
Pull request for series with
subject: NUMA: Early use of cpu_to_node() returns 0 instead of the correct node id
version: 1
url: https://patchwork.kernel.org/project/linux-riscv/list/?series=817993