driver-core/cpu: Expose hotpluggability to the rest of the kernel
authorJosh Triplett <josh@joshtriplett.org>
Sat, 3 Dec 2011 21:06:50 +0000 (13:06 -0800)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Sun, 11 Dec 2011 18:32:20 +0000 (10:32 -0800)
commit2987557f52b97f679f0c324d8f51b8d66e1f2084
tree93264730d265ef1987e45a97989d75b7a966dbab
parent2d1dc9a600edf33321bcdc1c808b7957d8a3f3e1
driver-core/cpu: Expose hotpluggability to the rest of the kernel

When architectures register CPUs, they indicate whether the CPU allows
hotplugging; notably, x86 and ARM don't allow hotplugging CPU 0.
Userspace can easily query the hotpluggability of a CPU via sysfs;
however, the kernel has no convenient way of accessing that property in
an architecture-independent way.  While the kernel can simply try it and
see, some code needs to distinguish between "hotplug failed" and
"hotplug has no hope of working on this CPU"; for example, rcutorture's
CPU hotplug tests want to avoid drowning out real hotplug failures with
expected failures.

Expose this property via a new cpu_is_hotpluggable function, so that the
rest of the kernel can access it in an architecture-independent way.

Signed-off-by: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
drivers/base/cpu.c
include/linux/cpu.h