[PW_SID:1128570] riscv: require vmemmap for NUMA balancing#2296
[PW_SID:1128570] riscv: require vmemmap for NUMA balancing#2296linux-riscv-bot wants to merge 2 commits into
Conversation
RISC-V randconfig can enable NUMA balancing while selecting SPARSEMEM_EXTREME without SPARSEMEM_VMEMMAP. In that layout, the section and node fields can consume enough page flag bits that LAST_CPUPID cannot fit in page->flags. The generic MM code then stores last_cpupid in struct page and emits the "Unfortunate NUMA and NUMA Balancing config" warning from mm/memory.c. NUMA balancing needs LAST_CPUPID storage, but this fallback grows struct page for a configuration that randconfig can select accidentally. Keep NUMA support available, but advertise RISC-V NUMA balancing support only when SPARSEMEM_VMEMMAP is enabled, where the page flag layout leaves room for LAST_CPUPID. This was originally seen with a RISC-V randconfig generated from KCONFIG_SEED=550012. Signed-off-by: Jia Wang <wangjia@ultrarisc.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
|
Patch 1: "riscv: require vmemmap for NUMA balancing" |
8ca72ef to
60e0882
Compare
2 participants
PR for series 1128570 applied to workflow__riscv__fixes
Name: riscv: require vmemmap for NUMA balancing
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=1128570
Version: 1