From fa06d58805c88f76f4454284c1e9e8334b559e30 Mon Sep 17 00:00:00 2001 From: Ingo Molnar Date: Thu, 15 May 2025 14:05:24 +0200 Subject: [PATCH] x86/boot/e820: Print E820_TYPE_RAM entries as ... RAM entries So it is a bit weird that the actual RAM entries of the E820 table are not actually called RAM, but 'usable': BIOS-e820: [mem 0x0000000000100000-0x000000007ffdbfff] 1.9 GB usable 'usable' is pretty passive-aggressive in that context and ambiguous, most E820 entries denote 'usable' address ranges - reserved ranges may be used by devices, or the platform. Clarify and disambiguate this by making the boot log entry explicitly say 'System RAM', like in /proc/iomem: BIOS-e820: [mem 0x0000000000100000-0x000000007ffdbfff] 1.9 GB System RAM Signed-off-by: Ingo Molnar Cc: Andy Shevchenko Cc: Arnd Bergmann Cc: Borislav Petkov Cc: Juergen Gross Cc: "H . Peter Anvin" Cc: Kees Cook Cc: Linus Torvalds Cc: Mike Rapoport Cc: Paul Menzel Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: David Woodhouse Link: https://patch.msgid.link/20250515120549.2820541-9-mingo@kernel.org --- arch/x86/kernel/e820.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c index 58001536ba7ca..b0efa4bf06325 100644 --- a/arch/x86/kernel/e820.c +++ b/arch/x86/kernel/e820.c @@ -188,7 +188,7 @@ void __init e820__range_add(u64 start, u64 size, enum e820_type type) static void __init e820_print_type(enum e820_type type) { switch (type) { - case E820_TYPE_RAM: pr_cont(" usable"); break; + case E820_TYPE_RAM: pr_cont(" System RAM"); break; case E820_TYPE_RESERVED: pr_cont(" reserved"); break; case E820_TYPE_SOFT_RESERVED: pr_cont(" soft reserved"); break; case E820_TYPE_ACPI: pr_cont(" ACPI data"); break; -- 2.47.3