linux-kernel - Re: [PATCH] x86: tidy e820 output

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C9A42E9.7040109@zytor.com>
Date:	Wed, 22 Sep 2010 10:54:49 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Yinghai Lu <yinghai@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: tidy e820 output

On 09/22/2010 10:27 AM, Bjorn Helgaas wrote:
> 
> This tidies e820 output by adding an "e820" prefix and printing ranges in
> the same style we use for struct resource with %pR, e.g.:
> 
>     - BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
>     + BIOS-e820: [mem 0x00000000-0x0009f3ff] (usable)
> 

I'm sorry, I have to admit to not understanding the difference.  I do
not want to change the number of hex digits from fixed 16 digits, as
that will make the output harder to read when printed in a block (as is
normal for the early e820 dump).  The [mem] prefix seems redundant with
(usable), or am I misreading this?

	-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/