Thread (13 messages) 13 messages, 2 authors, 2021-10-21
STALE1691d REVIEWED: 1 (0M)
Revisions (10)
  1. v15 current
  2. v16 [diff vs current]
  3. v17 [diff vs current]
  4. v18 [diff vs current]
  5. v19 [diff vs current]
  6. v20 [diff vs current]
  7. v21 [diff vs current]
  8. v22 [diff vs current]
  9. v23 [diff vs current]
  10. v24 [diff vs current]

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

From: Zhen Lei <hidden>
Date: 2021-10-20 02:14:47
Also in: kexec, linux-arm-kernel, linux-devicetree, lkml
Subsystem: the rest, x86 architecture (32-bit and 64-bit) · Maintainers: Linus Torvalds, Thomas Gleixner, Ingo Molnar, Borislav Petkov, Dave Hansen

From: Chen Zhou <redacted>

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 3d394127dc03d20..5bebd46c7ce81f5 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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help