Lines Matching refs:CPU
2 CPU hotplug in the Kernel
18 insertion and removal require support for CPU hotplug.
21 provisioning reasons, or for RAS purposes to keep an offending CPU off
22 system execution path. Hence the need for CPU hotplug support in the
25 A more novel use of CPU-hotplug support is its use today in suspend resume
58 CPU maps
71 after a CPU is available for kernel scheduling and ready to receive
72 interrupts from devices. Its cleared when a CPU is brought down using
74 migrated to another target CPU.
84 You really don't need to manipulate any of the system CPU maps. They should
87 ``for_each_cpu()`` can be used to iterate over a custom CPU mask.
92 Using CPU hotplug
114 The files *offline*, *online*, *possible*, *present* represent the CPU masks.
115 Each CPU folder contains an *online* file which controls the logical on (1) and
119 smpboot: CPU 4 is now offline
121 Once the CPU is shutdown, it will be removed from */proc/interrupts*,
128 The CPU is usable again. This should work on all CPUs. CPU0 is often special
129 and excluded from CPU hotplug. On X86 the kernel option
140 The CPU hotplug coordination
145 Once a CPU has been logically shutdown the teardown callbacks of registered
151 * All processes are migrated away from this outgoing CPU to new CPUs.
152 The new CPU is chosen from each process' current cpuset, which may be
154 * All interrupts targeted to this CPU are migrated to a new CPU
155 * timers are also migrated to a new CPU
161 It is possible to receive notifications once a CPU is offline or onlined. This
175 once a CPU is brought online and *Y_prepare_down* will be invoked when a
176 CPU is shutdown. All resources which were previously allocated in
218 removal of a state because usually the operation needs to performed once a CPU
223 ``get_online_cpus()`` and ``put_online_cpus()`` should be used to inhibit CPU
232 CPU is up.
234 just the after the CPU has been brought up. The interrupts are off and
235 the scheduler is not yet active on this CPU. Starting with *CPUHP_AP_OFFLINE*
236 the callbacks are invoked on the target CPU.
239 * The states are invoked in the reverse order on CPU shutdown starting with
241 invoked on the CPU that will be shutdown until *CPUHP_AP_OFFLINE*.
252 shutdown a CPU and then put it online again. It is also possible to put the CPU
288 # TASK-PID CPU# TIMESTAMP FUNCTION
327 Arch interface to bring up a CPU
330 Arch interface to shutdown a CPU, no more interrupts can be handled by the
334 This actually supposed to ensure death of the CPU. Actually look at some
335 example code in other arch that implement CPU hotplug. The processor is taken
342 After CPU successfully onlined or offline udev events are sent. A udev rule like: ::
352 echo "CPU ${DEVPATH##*/} offline"
356 echo "CPU ${DEVPATH##*/} online"