Lines Matching refs:to

6 The goal of firmware-assisted dump is to enable the dump of
7 a crashed system, and to do so from a fully-reset system, and
8 to minimize the total elapsed time until the system is back
11 - Firmware assisted dump (fadump) infrastructure is intended to replace
18 - Unlike phyp dump, userspace tool does not need to refer any sysfs
20 - Unlike phyp dump, fadump allows user to release all the memory reserved
35    is immediately available to the running kernel. And therefore,
36    unlike kdump, fadump doesn't need a 2nd reboot to get back
37    the system to the production configuration.
50    or 256MB) of RAM to the previous registered region. It will
54          that is required for a kernel to boot successfully when
61          kernel to boot successfully.
76 -- User-space tools will read /proc/vmcore to obtain the contents
78    format. The userspace tools may copy this info to disk, or
82    '1' to /sys/kernel/fadump_release_mem to release the reserved
83    memory back to general use, except the memory required for
96 During boot, a check is made to see if firmware supports
98 we check to see if an active dump is waiting for us. If yes
107 to hold CPU state, HPTE region, boot memory dump and elfcore
111 content in addition to CPU state and HPTE region, in the case a
127           Boot memory content gets transferred to
144    kernel to boot
147 Currently the dump will be copied from /proc/vmcore to a
150 infrastructure (kdump scripts) to save the dump works fine with
153 The tools to examine the dump will be same as the ones
156 How to enable firmware-assisted dump (fadump):
162    to specify size of the memory to reserve for boot memory dump
165 NOTE: If firmware-assisted dump fails to reserve memory then it will
166    fallback to existing kdump mechanism if 'crashkernel=' option
172 Firmware-assisted dump feature uses sysfs file system to hold
173 the control files and debugfs file to display memory reserved region.
179     This is used to display the fadump status.
183     This interface can be used by kdump init scripts to identify if
188     This is used to display the fadump registration status as well
189     as to control (start/stop) the fadump registration.
191     1 = fadump is registered and ready to handle system crash.
202     second kernel. This is used to release the reserved memory
204     reserved memory echo 1 to it:
209     file will change to reflect the new memory reservations.
212     enhanced to use this interface to release the memory reserved for
241 NOTE: Please refer to Documentation/filesystems/debugfs.txt on
242       how to mount the debugfs filesystem.
247  o Need to come up with the better approach to find out more
248    accurate boot memory size that is required for a kernel to
252    this structure is to pass some important crash info data to the second
253    kernel which will help second kernel to populate ELF core header with
256    additional fields (in future) to this structure without affecting
257    compatibility. Need to come up with the better approach to address this.
260 	whenever a new field is added to the structure in future. The version
261 	field can be used to find out what fields are valid for the current
264 	structure and have unused area as reserved (initialized to zero)
266    The advantage of approach 1 over 2 is we don't need to reserve extra space.