Lines Matching +full:cpu +full:- +full:release +full:- +full:addr
2 Firmware-Assisted Dump
7 The goal of firmware-assisted dump is to enable the dump of
8 a crashed system, and to do so from a fully-reset system, and
12 - Firmware-Assisted Dump (FADump) infrastructure is intended to replace
14 - Fadump uses the same firmware interfaces and memory reservation model
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
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
23 - Once enabled through kernel boot parameter, FADump can be
28 Comparing with kdump or other strategies, firmware-assisted
31 - Unlike kdump, the system has been reset, and loaded
35 - Once the dump is copied out, the memory that held the dump
44 - The first kernel registers the sections of memory with the
49 - When system crashes, the Power firmware will copy the registered
63 refer to Documentation/admin-guide/kdump/kdump.rst. If any
68 - After the low memory (boot memory) area has been saved, the
73 - The freshly booted kernel will notice that there is a new node
74 (rtas/ibm,kernel-dump on pSeries or ibm,opal/dump/mpipl-boot
83 - User-space tools will read /proc/vmcore to obtain the contents
88 - Once the userspace tool is done saving dump, it will echo
89 '1' to /sys/kernel/fadump_release_mem to release the reserved
91 next firmware-assisted dump registration.
97 Please note that the firmware-assisted dump feature
113 -- On OPAL based machines (PowerNV), if the kernel is build with
124 -----------------------
137 hold CPU state, HPTE region, boot memory dump, FADump header and
141 for a copy of the boot memory content in addition to CPU state and
157 0 boot memory size |<--- Reserved dump area --->| |
160 +-----------+-----/ /---+---+----+-------+-----+-----+----+--+
162 +-----------+-----/ /---+---+----+-------+-----+-----+----+--+
165 \ CPU HPTE / | |
166 ------------------------------ | |
187 | |<------------ Crash preserved area ------------>|
188 V V |<--- Reserved dump area --->| |
189 +-----------+-----/ /---+---+----+-------+-----+-----+----+--+
191 +-----------+-----/ /---+---+----+-------+-----+-----+----+--+
197 +---+
198 |///| -> Regions (CPU, HPTE & Metadata) marked like this in the above
199 +---+ figures are not always present. For example, OPAL platform
200 does not have CPU & HPTE regions while Metadata region is
217 How to enable firmware-assisted dump (FADump):
218 ----------------------------------------------
233 2. If firmware-assisted dump fails to reserve memory then it
242 --------------------
244 Firmware-assisted dump feature uses sysfs file system to hold
252 - 0 = FADump is disabled
253 - 1 = FADump is enabled
262 - 0 = FADump is not registered.
263 - 1 = FADump is registered and ready to handle system crash.
266 echo 0 > /sys/kernel/fadump_registered for un-register and stop the
267 FADump. Once the FADump is un-registered, the system crash will not
273 second kernel. This is used to release the reserved memory
274 region that are held for saving crash dump. To release the
283 enhanced to use this interface to release the memory reserved for
289 active during capture kernel. This is used to release the memory
291 release this memory, echo '1' to it:
303 <region>: [<start>-<end>] <reserved-size> bytes, Dumped: <dump-size>
307 DUMP: Src: <src-addr>, Dest: <dest-addr>, Size: <size>, Dumped: # bytes
313 CPU : [0x0000006ffb0000-0x0000006fff001f] 0x40020 bytes, Dumped: 0x0
314 HPTE: [0x0000006fff0020-0x0000006fff101f] 0x1000 bytes, Dumped: 0x0
315 DUMP: [0x0000006fff1020-0x0000007fff101f] 0x10000000 bytes, Dumped: 0x0
320 CPU : [0x0000006ffb0000-0x0000006fff001f] 0x40020 bytes, Dumped: 0x40020
321 HPTE: [0x0000006fff0020-0x0000006fff101f] 0x1000 bytes, Dumped: 0x1000
322 DUMP: [0x0000006fff1020-0x0000007fff101f] 0x10000000 bytes, Dumped: 0x10000000
323 : [0x00000010000000-0x0000006ffaffff] 0x5ffb0000 bytes, Dumped: 0x5ffb0000
332 -----
333 - Need to come up with the better approach to find out more
336 - The FADump implementation introduces a FADump crash info structure