Commit bc183779 authored by Hari Bathini's avatar Hari Bathini Committed by Michael Ellerman

powerpc/fadump: Update fadump documentation

With the unnecessary restriction to reserve memory for fadump at the
top of RAM forgone, update the documentation accordingly.
Signed-off-by: default avatarHari Bathini <hbathini@linux.vnet.ibm.com>
Signed-off-by: default avatarMichael Ellerman <mpe@ellerman.id.au>
parent f6e6bedb
...@@ -105,21 +105,21 @@ memory is held. ...@@ -105,21 +105,21 @@ memory is held.
If there is no waiting dump data, then only the memory required If there is no waiting dump data, then only the memory required
to hold CPU state, HPTE region, boot memory dump and elfcore to hold CPU state, HPTE region, boot memory dump and elfcore
header, is reserved at the top of memory (see Fig. 1). This area header, is usually reserved at an offset greater than boot memory
is *not* released: this region will be kept permanently reserved, size (see Fig. 1). This area is *not* released: this region will
so that it can act as a receptacle for a copy of the boot memory be kept permanently reserved, so that it can act as a receptacle
content in addition to CPU state and HPTE region, in the case a for a copy of the boot memory content in addition to CPU state
crash does occur. and HPTE region, in the case a crash does occur.
o Memory Reservation during first kernel o Memory Reservation during first kernel
Low memory Top of memory Low memory Top of memory
0 boot memory size | 0 boot memory size |
| | |<--Reserved dump area -->| | | |<--Reserved dump area -->| |
V V | Permanent Reservation V V V | Permanent Reservation | V
+-----------+----------/ /----------+---+----+-----------+----+ +-----------+----------/ /---+---+----+-----------+----+------+
| | |CPU|HPTE| DUMP |ELF | | | |CPU|HPTE| DUMP |ELF | |
+-----------+----------/ /----------+---+----+-----------+----+ +-----------+----------/ /---+---+----+-----------+----+------+
| ^ | ^
| | | |
\ / \ /
...@@ -135,12 +135,12 @@ crash does occur. ...@@ -135,12 +135,12 @@ crash does occur.
0 boot memory size | 0 boot memory size |
| |<------------- Reserved dump area ----------- -->| | |<------------- Reserved dump area ----------- -->|
V V V V V V
+-----------+----------/ /----------+---+----+-----------+----+ +-----------+----------/ /---+---+----+-----------+----+------+
| | |CPU|HPTE| DUMP |ELF | | | |CPU|HPTE| DUMP |ELF | |
+-----------+----------/ /----------+---+----+-----------+----+ +-----------+----------/ /---+---+----+-----------+----+------+
| | | |
V V V V
Used by second /proc/vmcore Used by second /proc/vmcore
kernel to boot kernel to boot
Fig. 2 Fig. 2
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment