diff options
author | Josh Triplett <josh@joshtriplett.org> | 2011-12-03 13:06:50 -0800 |
---|---|---|
committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2011-12-11 10:32:20 -0800 |
commit | 2987557f52b97f679f0c324d8f51b8d66e1f2084 (patch) | |
tree | 93264730d265ef1987e45a97989d75b7a966dbab /drivers/accessibility | |
parent | 2d1dc9a600edf33321bcdc1c808b7957d8a3f3e1 (diff) |
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>
Diffstat (limited to 'drivers/accessibility')
0 files changed, 0 insertions, 0 deletions