Lines Matching full:resume

11 state. Upon resume from hibernation, the hardware is restarted and the
12 memory image is restored from disk so that it can resume execution
19 Hibernation and resume happen on the same hardware, and Linux kernel
42 configuration between the hibernation and resume. Even when the resume
46 removed. Most such changes cause the resume steps to fail, though
51 virtual hardware configuration. While it is desirable for resume from
76 assigned memory, and the memory size mismatch causes resume to fail.
106 Handling VMBus Devices During Hibernation & Resume
109 implement suspend and resume functions that are called as part of the
115 device to be persisted across the hibernation/resume. When the VM
122 Documentation/virt/hyperv/vmbus.rst.) Upon resume from hibernation,
123 the resume functions expect that the devices offered by Hyper-V have
131 not matched with a device offered in the resumed VM, the resume
138 resume function matches the class/instance GUIDs, and updates the
148 so the channel data structure continues to exist. Upon resume, the
149 device driver's resume function re-allocates the ring buffer and
158 "poweroff" phases, and the same resume function for the "thaw" and
179 5. As part of the "thaw" phase, Linux PM calls the "resume" function
184 6. Linux PM calls the "resume" function for each VMBus device. Each
197 Detailed Resume Sequence
206 3. If this is a resume from hibernation, the "freeze" phase is used
213 5. As part of the "resume" phase, Linux PM repeats Steps 5 and 6
216    channels in the image. Relids are updated. VMBus device resume
218 6. Linux PM exits the hibernation resume sequence and the VM is now
230 resume sequence while still in the fresh OS instance. But in both
262 Sequence above and in the Detailed Resume Sequence. In such a case,
272 suspend and resume operations needed for hibernation. If a VMBus
284 customer VM, and the steps the Linux kernel takes to resume from the
290 would cause the resume from hibernation to fail, so several things are