diff options
| author | Hari Bathini <hbathini@linux.ibm.com> | 2024-02-26 16:00:08 +0530 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2024-03-17 13:34:00 +1100 |
| commit | 56a34d799bfa53064e7b8bd354aacd176aeaecc8 (patch) | |
| tree | 6a77826c83b50906952df9d55f89e532ada2fbc7 /arch/powerpc/kexec/elf_64.c | |
| parent | 78cb0945f7141961781f815168f6873ad2b7ed29 (diff) | |
| download | linux-stable-56a34d799bfa53064e7b8bd354aacd176aeaecc8.tar.gz linux-stable-56a34d799bfa53064e7b8bd354aacd176aeaecc8.tar.bz2 linux-stable-56a34d799bfa53064e7b8bd354aacd176aeaecc8.zip | |
kexec/kdump: make struct crash_mem available without CONFIG_CRASH_DUMP
struct crash_mem defined under include/linux/crash_core.h represents
a list of memory ranges. While it is used to represent memory ranges
for kdump kernel, it can also be used for other kind of memory ranges.
In fact, KEXEC_FILE_LOAD syscall in powerpc uses this structure to
represent reserved memory ranges and exclude memory ranges needed to
find the right memory regions to load kexec kernel. So, make the
definition of crash_mem structure available for !CONFIG_CRASH_DUMP
case too.
Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
Acked-by: Baoquan He <bhe@redhat.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20240226103010.589537-2-hbathini@linux.ibm.com
Diffstat (limited to 'arch/powerpc/kexec/elf_64.c')
0 files changed, 0 insertions, 0 deletions