Do not set cpu_possible_map to NR_CPUS bits when CPU hotplug is enabled
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Dont set NR_CPUS for cpu_possible_map when CPU hotplug is enabled. | +0 | 0 replies | |
| 2/2 | Count disabled cpus as potential hot-pluggable CPUs | +0 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
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