Thread (40 messages) 40 messages, 5 authors, 2021-02-26

Re: [PATCH v14 02/11] x86: kdump: make the lower bound of crash kernel reservation consistent

From: Baoquan He <bhe@redhat.com>
Date: 2021-02-18 03:35:35
Also in: linux-arm-kernel, lkml

On 01/30/21 at 03:10pm, Chen Zhou wrote:
quoted hunk ↗ jump to hunk
The lower bounds of crash kernel reservation and crash kernel low
reservation are different, use the consistent value CRASH_ALIGN.

Suggested-by: Dave Young <redacted>
Signed-off-by: Chen Zhou <redacted>
Tested-by: John Donnelly <redacted>
---
 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 da769845597d..27470479e4a3 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -439,7 +439,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);
Acked-by: Baoquan He <bhe@redhat.com>
 	if (!low_base) {
 		pr_err("Cannot reserve %ldMB crashkernel low memory, please try smaller size.\n",
 		       (unsigned long)(low_size >> 20));
-- 
2.20.1
  
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help