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 <t...@linutronix.de>
Cc: Ingo Molnar <mi...@redhat.com>
Cc: Borislav Petkov <b...@alien8.de>
Cc: "H. Peter Anvin" <h...@zytor.com>
Cc: Baoquan He <b...@redhat.com>
Cc: Will Deacon <will.dea...@arm.com>
Cc: Nicolas Pitre <n...@linaro.org>
Cc: Vivek Goyal <vgo...@redhat.com>
Cc: Chao Fan <fanc.f...@cn.fujitsu.com>
Cc: "Kirill A. Shutemov" <kirill.shute...@linux.intel.com>
Cc: Ard Biesheuvel <ard.biesheu...@linaro.org>
CC: Hari Bathini <hbath...@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
---
v3 -> v4:
reuse the parse_crashkernel_xx routines
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
