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
73 of them may be online. When physical hotplug is processed by the relevant
77 at which time hotplug is disabled.
87 Using CPU hotplug
104 drwxr-xr-x 2 root root 0 Dec 21 16:33 hotplug
125 and excluded from CPU hotplug.
127 The CPU hotplug coordination
134 hotplug states will be invoked, starting with ``CPUHP_ONLINE`` and terminating
148 The CPU hotplug API
151 CPU hotplug state machine
154 CPU hotplug uses a trivial state machine with a linear state space from
168 If a usage site requires only a callback in one direction of the hotplug
223 The callbacks are invoked in the context of the per CPU hotplug thread,
227 The callbacks are allowed to fail. When a callback fails the hotplug
321 The CPU hotplug state machine stops right here and does not try to go back
341 There are two ways to allocate a CPU hotplug state:
346 ordering requirements versus other CPU hotplug states. E.g. the PERF core
358 up at runtime and are part of the initializer of the CPU hotplug state
371 Setup of a CPU hotplug state
382 CPU hotplug state callbacks need to be invoked for each instance, the CPU
383 hotplug core provides multi-instance support. The advantage over driver
385 serialized against CPU hotplug operations and provide the automatic
442 section) in the context of the CPU's hotplug thread.
450 hotplug operations. If the setup function has to be called from a CPU
451 hotplug read locked region, then the _cpuslocked() variants have to be
452 used. These functions cannot be used from within CPU hotplug callbacks.
471 Removal of a CPU hotplug state
495 each online CPU (ONLINE section) in the context of the CPU's hotplug
501 hotplug operations. If the remove function has to be called from a CPU
502 hotplug read locked region, then the _cpuslocked() variants have to be
503 used. These functions cannot be used from within CPU hotplug callbacks.
535 on each online CPU (ONLINE section) in the context of the CPU's hotplug
562 CPU's hotplug thread.
567 serialized against CPU hotplug operations. These functions cannot be used
568 from within CPU hotplug callbacks and CPU hotplug read locked regions.
622 Testing of hotplug states
631 All registered states are enumerated in ``/sys/devices/system/cpu/hotplug/states`` ::
633 $ tail /sys/devices/system/cpu/hotplug/states
647 $ cat /sys/devices/system/cpu/cpu4/hotplug/state
649 $ echo 140 > /sys/devices/system/cpu/cpu4/hotplug/target
650 $ cat /sys/devices/system/cpu/cpu4/hotplug/state
656 $ echo 169 > /sys/devices/system/cpu/cpu4/hotplug/target
657 $ cat /sys/devices/system/cpu/cpu4/hotplug/state
710 example code in other arch that implement CPU hotplug. The processor is taken