Lines Matching +full:loop +full:- +full:powered

5 (C) 2011 - 2014 Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
8 I. Differences between CPU hotplug and Suspend-to-RAM
11 How does the regular CPU hotplug code differ from how the Suspend-to-RAM
14 Well, a picture is worth a thousand words... So ASCII art follows :-)
21 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
24 On a high level, the suspend-resume cycle goes like this::
26   |Freeze| -> |Disable nonboot| -> |Do suspend| -> |Enable nonboot| -> |Thaw |
33                                 -----------------
62                                         |                ----------
76                                 frozen_cpus mask         ----------
100    |  Call _cpu_up() [for all those cpus in the frozen_cpus mask, in a loop]
118                           -----------------------------
158 the non-boot CPUs are offlined or onlined, the _cpu_*() functions are called
164 -------------------------------------------
166 - kernel/power/process.c : freeze_processes(), thaw_processes()
167 - kernel/power/suspend.c : suspend_prepare(), suspend_enter(), suspend_finish()
168 - kernel/cpu.c: cpu_[up|down](), _cpu_[up|down](),
174 ------------------------------------------------
203 c. When a CPU is physically hot-unplugged and a new (and possibly different
204    type of) CPU is hot-plugged into the system:
229    physically removing or inserting CPUs, the CPUs are not actually powered
230    off during a CPU offline. They are just put to the lowest C-states possible.
231    Hence, in such a case, it is not really necessary to re-apply microcode
237    powered off, during restore it becomes necessary to apply the microcode
241    nodes with a different type of CPUs in-between a suspend-resume or a
249    CPUs, it just applies them to the CPUs, avoiding any re-discovery of CPU
252    hotplug will not be done in-between suspend/resume or hibernate/restore
267    tasks could have been frozen by an out-of-band event such as a suspend