Lines Matching refs:hotplug
2 CPU hotplug in the Kernel
19 insertion and removal require support for CPU hotplug.
23 system execution path. Hence the need for CPU hotplug support in the
26 A more novel use of CPU-hotplug support is its use today in suspend resume
79 of them may be online. When physical hotplug is processed by the relevant
83 at which time hotplug is disabled.
93 Using CPU hotplug
110 drwxr-xr-x 2 root root 0 Dec 21 16:33 hotplug
131 and excluded from CPU hotplug. On X86 the kernel option
142 The CPU hotplug coordination
149 hotplug states will be invoked, starting with ``CPUHP_ONLINE`` and terminating
163 The CPU hotplug API
166 CPU hotplug state machine
169 CPU hotplug uses a trivial state machine with a linear state space from
183 If a usage site requires only a callback in one direction of the hotplug
238 The callbacks are invoked in the context of the per CPU hotplug thread,
242 The callbacks are allowed to fail. When a callback fails the hotplug
336 The CPU hotplug state machine stops right here and does not try to go back
356 There are two ways to allocate a CPU hotplug state:
361 ordering requirements versus other CPU hotplug states. E.g. the PERF core
373 up at runtime and are part of the initializer of the CPU hotplug state
386 Setup of a CPU hotplug state
397 CPU hotplug state callbacks need to be invoked for each instance, the CPU
398 hotplug core provides multi-instance support. The advantage over driver
400 serialized against CPU hotplug operations and provide the automatic
457 section) in the context of the CPU's hotplug thread.
465 hotplug operations. If the setup function has to be called from a CPU
466 hotplug read locked region, then the _cpuslocked() variants have to be
467 used. These functions cannot be used from within CPU hotplug callbacks.
486 Removal of a CPU hotplug state
510 each online CPU (ONLINE section) in the context of the CPU's hotplug
516 hotplug operations. If the remove function has to be called from a CPU
517 hotplug read locked region, then the _cpuslocked() variants have to be
518 used. These functions cannot be used from within CPU hotplug callbacks.
550 on each online CPU (ONLINE section) in the context of the CPU's hotplug
577 CPU's hotplug thread.
582 serialized against CPU hotplug operations. These functions cannot be used
583 from within CPU hotplug callbacks and CPU hotplug read locked regions.
637 Testing of hotplug states
646 All registered states are enumerated in ``/sys/devices/system/cpu/hotplug/states`` ::
648 $ tail /sys/devices/system/cpu/hotplug/states
662 $ cat /sys/devices/system/cpu/cpu4/hotplug/state
664 $ echo 140 > /sys/devices/system/cpu/cpu4/hotplug/target
665 $ cat /sys/devices/system/cpu/cpu4/hotplug/state
671 $ echo 169 > /sys/devices/system/cpu/cpu4/hotplug/target
672 $ cat /sys/devices/system/cpu/cpu4/hotplug/state
725 example code in other arch that implement CPU hotplug. The processor is taken