crashkernel=x@y or or =range1:size1[,range2:size2,...]@offset option may fail to reserve the required memory region if KASLR puts kernel into the region. To avoid this uncertainty, asking KASLR to skip the required region. And the parsing routine can be re-used at this early boot stage.
Cc: Thomas Gleixner <[email protected]> Cc: Ingo Molnar <[email protected]> Cc: Borislav Petkov <[email protected]> Cc: "H. Peter Anvin" <[email protected]> Cc: Baoquan He <[email protected]> Cc: Will Deacon <[email protected]> Cc: Nicolas Pitre <[email protected]> Cc: Vivek Goyal <[email protected]> Cc: Chao Fan <[email protected]> Cc: "Kirill A. Shutemov" <[email protected]> Cc: Ard Biesheuvel <[email protected]> CC: Hari Bathini <[email protected]> Cc: [email protected] --- v3 -> v4: reuse the parse_crashkernel_xx routines v4 -> v5: drop unnecessary initialization of crash_base in [2/2] Pingfan Liu (2): kernel/crash_core: separate the parsing routines to lib/parse_crashkernel.c x86/boot/KASLR: skip the specified crashkernel region arch/x86/boot/compressed/kaslr.c | 40 ++++++ kernel/crash_core.c | 273 ------------------------------------ lib/Makefile | 2 + lib/parse_crashkernel.c | 289 +++++++++++++++++++++++++++++++++++++++ 4 files changed, 331 insertions(+), 273 deletions(-) create mode 100644 lib/parse_crashkernel.c -- 2.7.4
