Lines Matching refs:suspend

19 On a high level, the suspend-resume cycle goes like this:
21 |Freeze| -> |Disable nonboot| -> |Do suspend| -> |Enable nonboot| -> |Thaw |
84                                    Do suspend
103 beginning, when we are just starting out to suspend, and then released only
104 after the entire cycle is complete (i.e., suspend + resume).
145 regular CPU hotplug and the suspend code path converge at the _cpu_down() and
148 argument. But during suspend, since the tasks are already frozen by the time
158 kernel/power/suspend.c : suspend_prepare(), suspend_enter(), suspend_finish()
216 d. Handling microcode update during suspend/hibernate:
225    This is the usual scenario encountered during a resume after a suspend.
231    nodes with a different type of CPUs in-between a suspend-resume or a
235    as part of the suspend/hibernate cycle (the CPU_DEAD_FROZEN notification),
242    hotplug will not be done in-between suspend/resume or hibernate/restore
246 III. Are there any known problems when regular CPU hotplug and suspend race
254    tasks could have been frozen by an out-of-band event such as a suspend
261    to a suspend operation in progress at the same time, then we could hit the
274    As a result of this task freezing failure, the suspend operation gets