[PATCH RESEND] ARM: kdump: 2nd kernel should use strict pfn_valid in SPARSEMEM platform
wangnan0 at huawei.com
Wed May 28 01:44:28 PDT 2014
This patch removes an irrational limitation for crash dump kernel on ARM
platform with SPARSEMEM enabled.
Without this patch, crash reservation area for a crash dump kernel with
SPARSEMEM selected must occupy a full section plus 1MiB. If not,
elfcorehdr and some memory space used by the first kernel will unable to
get accessed. This is caused by pfn_valid: fast pfn_valid ragards any
pfn in a valid section as valid and prevents it to be ioremapped.
This limitation wastes memory, because sections are always large and
crash dump kernel should be as small as possible.
This patch selects HAVE_ARCH_PFN_VALID for CRASH_DUMP, makes crash dump
kernel to use strict version of pfn_valid().
Signed-off-by: Wang Nan <wangnan0 at huawei.com>
This is the third time I post this patch. The previous records can be
Different from previous version, this patch select HAVE_ARCH_PFN_VALID
right after CRASH_DUMP config entry.
arch/arm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index c57ddcb..d5ffbb1 100644
@@ -2160,6 +2160,7 @@ config ATAGS_PROC
bool "Build kdump crash kernel (EXPERIMENTAL)"
+ select HAVE_ARCH_PFN_VALID if SPARSEMEM
Generate crash dump after being started by kexec. This should
be normally only set in special crash dump kernels which are
More information about the kexec