Skip to content

Commit fa06d58

Browse files
committed
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 <mingo@kernel.org> Cc: Andy Shevchenko <andy@kernel.org> Cc: Arnd Bergmann <arnd@kernel.org> Cc: Borislav Petkov <bp@alien8.de> Cc: Juergen Gross <jgross@suse.com> Cc: "H . Peter Anvin" <hpa@zytor.com> Cc: Kees Cook <keescook@chromium.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Mike Rapoport <rppt@kernel.org> Cc: Paul Menzel <pmenzel@molgen.mpg.de> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: David Woodhouse <dwmw@amazon.co.uk> Link: https://patch.msgid.link/20250515120549.2820541-9-mingo@kernel.org
1 parent c87f944 commit fa06d58

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

arch/x86/kernel/e820.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -188,7 +188,7 @@ void __init e820__range_add(u64 start, u64 size, enum e820_type type)
188188
static void __init e820_print_type(enum e820_type type)
189189
{
190190
switch (type) {
191-
case E820_TYPE_RAM: pr_cont(" usable"); break;
191+
case E820_TYPE_RAM: pr_cont(" System RAM"); break;
192192
case E820_TYPE_RESERVED: pr_cont(" reserved"); break;
193193
case E820_TYPE_SOFT_RESERVED: pr_cont(" soft reserved"); break;
194194
case E820_TYPE_ACPI: pr_cont(" ACPI data"); break;

0 commit comments

Comments
 (0)