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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.1009221622410.27644@chino.kir.corp.google.com>
Date:	Wed, 22 Sep 2010 16:27:16 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	"H. Peter Anvin" <hpa@...or.com>
cc:	Bjorn Helgaas <bjorn.helgaas@...com>,
	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 Wed, 22 Sep 2010, H. Peter Anvin wrote:

> > I'm referring to using [start, start + addr - 1] in the output, like 
> > /sys/firmware/memmap does, as opposed to [start, start + addr].  Is it not 
> > valuable to include the actual e820 map in some way, especially when you 
> > have your own BIOS?  We've always used this output since it isn't 
> > available later.
> 
> "The actual e820 map" contains (start, length, type) -- the end bracket
> is not part of it at all.  Either way, /sys/firmware/memmap does provide
> the memory map as provided by the firmware through whatever means.
> 

Ok, I agree that fixing the off-by-1 problem that's been there for ages is 
better and worth modifying our scripts when they break.  Thanks!
--
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/