[PATCH v17 02/10] x86: kdump: make the lower bound of crash kernel reservation consistent

Zhen Lei thunder.leizhen at huawei.com
Thu Dec 9 22:55:25 PST 2021


From: Chen Zhou <chenzhou10 at huawei.com>

The lower bounds of crash kernel reservation and crash kernel low
reservation are different, use the consistent value CRASH_ALIGN.

Suggested-by: Dave Young <dyoung at redhat.com>
Signed-off-by: Chen Zhou <chenzhou10 at huawei.com>
Signed-off-by: Zhen Lei <thunder.leizhen at huawei.com>
Tested-by: John Donnelly <John.p.donnelly at oracle.com>
Tested-by: Dave Kleikamp <dave.kleikamp at oracle.com>
---
 arch/x86/kernel/setup.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 5cc60996eac56d6..6424ee4f23da2cf 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -441,7 +441,8 @@ static int __init reserve_crashkernel_low(void)
 			return 0;
 	}
 
-	low_base = memblock_phys_alloc_range(low_size, CRASH_ALIGN, 0, CRASH_ADDR_LOW_MAX);
+	low_base = memblock_phys_alloc_range(low_size, CRASH_ALIGN, CRASH_ALIGN,
+			CRASH_ADDR_LOW_MAX);
 	if (!low_base) {
 		pr_err("Cannot reserve %ldMB crashkernel low memory, please try smaller size.\n",
 		       (unsigned long)(low_size >> 20));
-- 
2.25.1




More information about the linux-arm-kernel mailing list