Lines Matching refs:dump
7 The goal of firmware-assisted dump is to enable the dump of
13 the existing phyp assisted dump.
15 as phyp assisted dump.
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
18 kdump infrastructure for dump capture and filtering.
19 - Unlike phyp dump, userspace tool does not need to refer any sysfs
21 - Unlike phyp dump, FADump allows user to release all the memory reserved
22 for dump, with a single operation of echo 1 > /sys/kernel/fadump_release_mem.
29 dump offers several strong, practical advantages:
35 - Once the dump is copied out, the memory that held the dump
45 Power firmware for dump preservation during OS initialization.
66 for boot memory dump preservation in case of a crash.
74 (rtas/ibm,kernel-dump on pSeries or ibm,opal/dump/mpipl-boot
81 of the dump memory area.
84 of memory, which holds the previous crashed kernel dump in ELF
88 - Once the userspace tool is done saving dump, it will echo
91 next firmware-assisted dump registration.
97 Please note that the firmware-assisted dump feature
101 Note that, OPAL firmware exports ibm,opal/dump node when
128 we check to see if an active dump is waiting for us. If yes
131 collecting the dump from user land scripts (e.g. kdump scripts)
132 that are run. If there is dump data, then the
136 If there is no waiting dump data, then only the memory required to
137 hold CPU state, HPTE region, boot memory dump, FADump header and
157 0 boot memory size |<--- Reserved dump area --->| |
178 to process the crashdump eases dump capture process.
188 V V |<--- Reserved dump area --->| |
206 Currently the dump will be copied from /proc/vmcore to a new file upon
207 user intervention. The dump data available through /proc/vmcore will be
209 to save the dump works fine with minor modifications. KDump scripts on
211 user intervention in saving the dump) when FADump is used, instead of
212 KDump, as dump mechanism.
214 The tools to examine the dump will be same as the ones
217 How to enable firmware-assisted dump (FADump):
226 to specify size of the memory to reserve for boot memory dump
232 for boot memory dump preservation.
233 2. If firmware-assisted dump fails to reserve memory then it
244 Firmware-assisted dump feature uses sysfs file system to hold
274 crash dump.
279 region that are held for saving crash dump. To release the
289 dump and continue without 2nd reboot.
323 <region>: [<start>-<end>] <reserved-size> bytes, Dumped: <dump-size>
381 assisted dump by Linas Vepstas and Manish Ahuja.