Lines Matching +full:step +full:- +full:up
25 A more novel use of CPU-hotplug support is its use today in suspend resume
26 support for SMP. Dual-core and HT support makes even a laptop run SMP kernels
80 from the map depending on the event is hot-add/hot-remove. There are currently
85 be read-only for most use. When setting up per-cpu resources almost always use
98 $ ls -lh /sys/devices/system/cpu
100 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu0
101 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu1
102 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu2
103 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu3
104 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu4
105 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu5
106 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu6
107 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu7
108 drwxr-xr-x 2 root root 0 Dec 21 16:33 hotplug
109 -r--r--r-- 1 root root 4.0K Dec 21 16:33 offline
110 -r--r--r-- 1 root root 4.0K Dec 21 16:33 online
111 -r--r--r-- 1 root root 4.0K Dec 21 16:33 possible
112 -r--r--r-- 1 root root 4.0K Dec 21 16:33 present
144 ----------------
160 ---------------------
163 or clean up functions based on the number of available CPUs: ::
190 callback independently then it is likely that a ''multi-state'' should be used.
191 First a multi-state state needs to be registered: ::
202 ret = cpuhp_state_add_instance(Y_hp_online, &d->node);
207 hlist_node`` member of your per-instance data structure.
210 cpuhp_state_remove_instance(Y_hp_online, &d->node)
228 --------------------------
232 CPU is up.
234 just the after the CPU has been brought up. The interrupts are off and
244 However if an earlier invocation during the bring up or shutdown is required
263 141: acpi/cpu-drv:online
288 # TASK-PID CPU# TIMESTAMP FUNCTION
290 bash-394 [001] 22.976: cpuhp_enter: cpu: 0004 target: 140 step: 169 (cpuhp_kick_ap_work)
291 cpuhp/4-31 [004] 22.977: cpuhp_enter: cpu: 0004 target: 140 step: 168 (sched_cpu_deactivate)
292 cpuhp/4-31 [004] 22.990: cpuhp_exit: cpu: 0004 state: 168 step: 168 ret: 0
293 cpuhp/4-31 [004] 22.991: cpuhp_enter: cpu: 0004 target: 140 step: 144 (mce_cpu_pre_down)
294 cpuhp/4-31 [004] 22.992: cpuhp_exit: cpu: 0004 state: 144 step: 144 ret: 0
295 …cpuhp/4-31 [004] 22.993: cpuhp_multi_enter: cpu: 0004 target: 140 step: 143 (virtnet_cpu_down_p…
296 cpuhp/4-31 [004] 22.994: cpuhp_exit: cpu: 0004 state: 143 step: 143 ret: 0
297 cpuhp/4-31 [004] 22.995: cpuhp_enter: cpu: 0004 target: 140 step: 142 (cacheinfo_cpu_pre_down)
298 cpuhp/4-31 [004] 22.996: cpuhp_exit: cpu: 0004 state: 142 step: 142 ret: 0
299 bash-394 [001] 22.997: cpuhp_exit: cpu: 0004 state: 140 step: 169 ret: 0
300 bash-394 [005] 95.540: cpuhp_enter: cpu: 0004 target: 169 step: 140 (cpuhp_kick_ap_work)
301 cpuhp/4-31 [004] 95.541: cpuhp_enter: cpu: 0004 target: 169 step: 141 (acpi_soft_cpu_online)
302 cpuhp/4-31 [004] 95.542: cpuhp_exit: cpu: 0004 state: 141 step: 141 ret: 0
303 cpuhp/4-31 [004] 95.543: cpuhp_enter: cpu: 0004 target: 169 step: 142 (cacheinfo_cpu_online)
304 cpuhp/4-31 [004] 95.544: cpuhp_exit: cpu: 0004 state: 142 step: 142 ret: 0
305 …cpuhp/4-31 [004] 95.545: cpuhp_multi_enter: cpu: 0004 target: 169 step: 143 (virtnet_cpu_online)
306 cpuhp/4-31 [004] 95.546: cpuhp_exit: cpu: 0004 state: 143 step: 143 ret: 0
307 cpuhp/4-31 [004] 95.547: cpuhp_enter: cpu: 0004 target: 169 step: 144 (mce_cpu_online)
308 cpuhp/4-31 [004] 95.548: cpuhp_exit: cpu: 0004 state: 144 step: 144 ret: 0
309 cpuhp/4-31 [004] 95.549: cpuhp_enter: cpu: 0004 target: 169 step: 145 (console_cpu_notify)
310 cpuhp/4-31 [004] 95.550: cpuhp_exit: cpu: 0004 state: 145 step: 145 ret: 0
311 cpuhp/4-31 [004] 95.551: cpuhp_enter: cpu: 0004 target: 169 step: 168 (sched_cpu_activate)
312 cpuhp/4-31 [004] 95.552: cpuhp_exit: cpu: 0004 state: 168 step: 168 ret: 0
313 bash-394 [005] 95.553: cpuhp_exit: cpu: 0004 state: 169 step: 140 ret: 0
315 As it an be seen, CPU4 went down until timestamp 22.996 and then back up until
327 Arch interface to bring up a CPU
365 .. kernel-doc:: include/linux/cpuhotplug.h