Skip to content

Do not set cpu_possible_map to NR_CPUS bits when CPU hotplug is enabled

Ashok Raj linux-ia64 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 2 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2Dont set NR_CPUS for cpu_possible_map when CPU hotplug is enabled.+0 -00 replies
2/2Count disabled cpus as potential hot-pluggable CPUs+0 -02 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [patch 0/2] Do not set cpu_possible_map to NR_CPUS bits when CPU hotplug is enabled

Hi Tony,

here is patch to not set NR_CPUS bits in cpu_possible_map when CONFIG_HOTPLUG_CPU is enabled. This just restricts the cpu_possible_map to a more reasonable number. We now count the number of disabled cpus in MADT as potentially hotpluggable cpus. In case thats not true, parameter additional_cpus=x can be used at startup to add extra bits to cpu_possible_map.

Will be good to fix it before 2.6.16 gets released. Other arch code is mostly checked in already I think.

Cheers,
ashok