summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorabuehaze14 <abuehaze@amazon.com>2022-04-19 17:23:27 +0000
committerSimon Horman <horms@kernel.org>2022-04-29 11:58:08 +0200
commit1b87ea9ccaf0993e53a6ed817359a4e1edf6862f (patch)
tree5f678aa270be559e9fca218f6b7173d067410d09
parent2ddfaf31fa8396a16e26409e80ed74ab330fbec8 (diff)
downloadkexec-tools-1b87ea9ccaf0993e53a6ed817359a4e1edf6862f.tar.gz
arm64/crashdump-arm64: increase CRASH_MAX_MEMORY_RANGES to 32k
On ARM64 based VMs hotplugging more than 31GB of memory will cause kdump to fail loading as it's hitting the CRASH_MAX_MEMORY_RANGES limit which is currently 32 on ARM64 given that the memory block size is 1GB. This patch is raising CRASH_MAX_MEMORY_RANGES to 32K similar to what we have on x86, this should allow kdump to work until the VM has 32TB which should be enough for a long time. Signed-off-by: Hazem Mohamed Abuelfotoh <abuehaze@amazon.com> Acked-by: Baoquan He <bhe@redhat.com> Signed-off-by: Simon Horman <horms@kernel.org>
-rw-r--r--kexec/arch/arm64/crashdump-arm64.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/kexec/arch/arm64/crashdump-arm64.h b/kexec/arch/arm64/crashdump-arm64.h
index 12f4308..82fa69b 100644
--- a/kexec/arch/arm64/crashdump-arm64.h
+++ b/kexec/arch/arm64/crashdump-arm64.h
@@ -14,7 +14,7 @@
#include "kexec.h"
-#define CRASH_MAX_MEMORY_RANGES 32
+#define CRASH_MAX_MEMORY_RANGES 32768
/* crash dump kernel support at most two regions, low_region and high region. */
#define CRASH_MAX_RESERVED_RANGES 2