Lines Matching full: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.
133 The CPU hotplug coordination
140 hotplug states will be invoked, starting with ``CPUHP_ONLINE`` and terminating
154 The CPU hotplug API
157 CPU hotplug state machine
160 CPU hotplug uses a trivial state machine with a linear state space from
174 If a usage site requires only a callback in one direction of the hotplug
229 The callbacks are invoked in the context of the per CPU hotplug thread,
233 The callbacks are allowed to fail. When a callback fails the hotplug
327 The CPU hotplug state machine stops right here and does not try to go back
347 There are two ways to allocate a CPU hotplug state:
352 ordering requirements versus other CPU hotplug states. E.g. the PERF core
364 up at runtime and are part of the initializer of the CPU hotplug state
377 Setup of a CPU hotplug state
388 CPU hotplug state callbacks need to be invoked for each instance, the CPU
389 hotplug core provides multi-instance support. The advantage over driver
391 serialized against CPU hotplug operations and provide the automatic
448 section) in the context of the CPU's hotplug thread.
456 hotplug operations. If the setup function has to be called from a CPU
457 hotplug read locked region, then the _cpuslocked() variants have to be
458 used. These functions cannot be used from within CPU hotplug callbacks.
477 Removal of a CPU hotplug state
501 each online CPU (ONLINE section) in the context of the CPU's hotplug
507 hotplug operations. If the remove function has to be called from a CPU
508 hotplug read locked region, then the _cpuslocked() variants have to be
509 used. These functions cannot be used from within CPU hotplug callbacks.
541 on each online CPU (ONLINE section) in the context of the CPU's hotplug
568 CPU's hotplug thread.
573 serialized against CPU hotplug operations. These functions cannot be used
574 from within CPU hotplug callbacks and CPU hotplug read locked regions.
628 Testing of hotplug states
637 All registered states are enumerated in ``/sys/devices/system/cpu/hotplug/states`` ::
639 $ tail /sys/devices/system/cpu/hotplug/states
653 $ cat /sys/devices/system/cpu/cpu4/hotplug/state
655 $ echo 140 > /sys/devices/system/cpu/cpu4/hotplug/target
656 $ cat /sys/devices/system/cpu/cpu4/hotplug/state
662 $ echo 169 > /sys/devices/system/cpu/cpu4/hotplug/target
663 $ cat /sys/devices/system/cpu/cpu4/hotplug/state
716 example code in other arch that implement CPU hotplug. The processor is taken