Lines Matching refs:dump

6 The goal of firmware-assisted dump is to enable the dump of
11 - Firmware assisted dump (fadump) infrastructure is intended to replace
12 the existing phyp assisted dump.
14 as phyp assisted dump.
15 - Unlike phyp dump, fadump exports the memory dump through /proc/vmcore
17 kdump infrastructure for dump capture and filtering.
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
21 for dump, with a single operation of echo 1 > /sys/kernel/fadump_release_mem.
28 dump offers several strong, practical advantages:
34 -- Once the dump is copied out, the memory that held the dump
44 Power firmware for dump preservation during OS initialization.
69 node (ibm,dump-kernel) in the device tree, indicating that
74 touch any of the dump memory area.
77 of memory, which holds the previous crashed kernel dump in ELF
81 -- Once the userspace tool is done saving dump, it will echo
84 next firmware-assisted dump registration.
89 Please note that the firmware-assisted dump feature
98 we check to see if an active dump is waiting for us. If yes
101 collecting the dump from user land scripts (e.g. kdump scripts)
102 that are run. If there is dump data, then the
106 If there is no waiting dump data, then only the memory required
107 to hold CPU state, HPTE region, boot memory dump and elfcore
118 | | |<--Reserved dump area -->|
136 | |<------------- Reserved dump area ----------- -->|
147 Currently the dump will be copied from /proc/vmcore to a
148 a new file upon user intervention. The dump data available through
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
172 Firmware-assisted dump feature uses sysfs file system to hold
203 region that are held for saving crash dump. To release the
213 dump and continue without 2nd reboot.
223 <region>: [<start>-<end>] <reserved-size> bytes, Dumped: <dump-size>
270 assisted dump by Linas Vepstas and Manish Ahuja.