Lines Matching refs:memory

14 - Fadump uses the same firmware interfaces and memory reservation model
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
21 - Unlike phyp dump, FADump allows user to release all the memory reserved
35 -  Once the dump is copied out, the memory that held the dump
44 -  The first kernel registers the sections of memory with the
46    These registered sections of memory are reserved by the first
50    low memory regions (boot memory) from source to destination area.
54          The term 'boot memory' means size of the low memory chunk
56          booted with restricted memory. By default, the boot memory
58          Alternatively, user can also specify boot memory size
61          boot memory size is not sufficient for second kernel to
65          ignored as FADump uses a predefined offset to reserve memory
66          for boot memory dump preservation in case of a crash.
68 -  After the low memory (boot memory) area has been saved, the
77    the early boot OS will reserve rest of the memory above
78    boot memory size effectively booting with restricted memory
81    of the dump memory area.
84    of memory, which holds the previous crashed kernel dump in ELF
90    memory back to general use, except the memory required for
108 preserve previously crash'ed kernel's memory for the subsequent
114    CONFIG_OPAL_CORE=y, OPAL memory at the time of crash is also
116    helpful in debugging OPAL crashes with GDB. The kernel memory
127    and to reduce its memory footprint while collecting the dump.
151 then everything but boot memory size of RAM is reserved during
156 memory is held.
158 If there is no waiting dump data, then only the memory required to
159 hold CPU state, HPTE region, boot memory dump, and FADump header is
160 usually reserved at an offset greater than boot memory size (see Fig. 1).
163 memory content in addition to CPU state and HPTE region, in the case
166 Since this reserved memory area is used only after the system crash,
167 there is no point in blocking this significant chunk of memory from
169 Contiguous Memory Allocator (CMA) for memory reservation if CMA is
170 configured for kernel. With CMA reservation this memory will be
173 kernel memory and most of the user space memory except the user pages
178   Low memory                                                  Top of memory
179   0    boot memory size   |<------ Reserved dump area ----->|     |
189       Boot memory content gets transferred         |      |
207   Low memory                                              Top of memory
208   0      boot memory size                                      |
236         Note: Memory from 0 to the boot memory size is used by second kernel
257    By default, FADump reserved memory will be initialized as CMA area.
261    to specify size of the memory to reserve for boot memory dump
266         use 'crashkernel=' to specify size of the memory to reserve
267         for boot memory dump preservation.
268      2. If firmware-assisted dump fails to reserve memory then it
271      3. if user wants to capture all of user space memory and ok with
272         reserved memory not available to production system, then
280 the control files and debugfs file to display memory reserved region.
308    This is used to display the memory reserved by FADump for saving the
313     second kernel. This is used to release the reserved memory
315     reserved memory echo 1 to it::
320     file will change to reflect the new memory reservations.
323     enhanced to use this interface to release the memory reserved for
332     active during capture kernel. This is used to release the memory
334     release this memory, echo '1' to it:
354     This file shows the reserved memory regions if FADump is
389    accurate boot memory size that is required for a kernel to
390    boot successfully when booted with restricted memory.