On Wed, 24 Jun 2020, Srikar Dronamraju wrote: > Currently Linux kernel with CONFIG_NUMA on a system with multiple > possible nodes, marks node 0 as online at boot. However in practice, > there are systems which have node 0 as memoryless and cpuless. Maybe add something to explain why you are not simply mapping the existing memory to NUMA node 0 which is after all just a numbering scheme used by the kernel and can be used arbitrarily? This could be seen more as a bug in the arch code during the setup of NUMA nodes. The two nodes are created by the firmwware / bootstrap code after all. Just do not do it?
