Lines Matching +full:suspend +full:- +full:to +full:- +full:ram
2 Documentation for userland software suspend interface
12 Now, to use the userland interface for software suspend you need special
13 utilities that will read/write the system memory snapshot from/to the
15 <http://suspend.sourceforge.net>. You may want to have a look at them if you
16 are going to develop your own suspend/resume utilities.
25 reading, it is considered to be in the suspend mode. Otherwise it is
26 assumed to be in the resume mode. The device cannot be open for simultaneous
27 reading and writing. It is also impossible to have the device open more than
39 and SNAPSHOT_ATOMIC_RESTORE to succeed
46 last argument of ioctl() should be a pointer to an int variable,
51 has been created the read() operation can be used to transfer
57 the system memory snapshot back to the kernel using the write()
59 image is not available to the kernel
66 (the kernel will do its best to ensure the image size will not exceed
67 this number, but if it turns out to be impossible, the kernel will
72 (the last argument should be a pointer to a loff_t variable that
77 (the last argument should be a pointer to a loff_t variable that
82 (the last argument should be a pointer to a loff_t variable that
92 located (the last ioctl() argument should point to a struct
96 swap files (see Documentation/power/swsusp-and-swap-files.rst for
104 make the kernel transition the system to the hibernation
108 suspend to RAM; using this call causes the kernel to
109 immediately enter the suspend-to-RAM state, so this call must always
111 to use the SNAPSHOT_UNFREEZE call after the system wakes up. This call
112 is needed to implement the suspend-to-both mechanism in which the
113 suspend image is first created, as though the system had been suspended
114 to disk, and then the system is suspended to RAM (this makes it possible
115 to resume the system from RAM if there's enough battery power or restore
116 its state on the basis of the saved suspend image otherwise)
118 The device's read() operation can be used to transfer the snapshot image from
121 - you cannot read() more than one virtual memory page at a time
122 - read()s across page boundaries are impossible (ie. if you read() 1/2 of
123 a page in the previous call, you will only be able to read()
131 Thus it is not necessary to use either SNAPSHOT_FREE or
137 snapshot image from/to the kernel will use a swap partition, called the resume
140 required, as they can use, for example, a special (blank) suspend partition or
148 The snapshot image MUST be written to the kernel unaltered (ie. all of the image
156 SNAPSHOT_ATOMIC_RESTORE will not succeed. Still, this is not a fool-proof
158 means, such as checksums, to ensure the integrity of the snapshot image.
164 in the memory location pointed to by the last argument of ioctl() and proceed
171 _unless_ the whole suspend procedure is to be cancelled, in
174 its header. If the suspend is not to be cancelled, the
177 (b) The suspending utility SHOULD NOT attempt to perform any
189 The resuming utility SHOULD NOT attempt to mount any file systems that could
190 be mounted before suspend and SHOULD NOT attempt to perform any operations
193 For details, please refer to the source code.