linux-kernel - Re: early_res and find_e820

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: <20080304104853.GA19022@elte.hu>
Date:	Tue, 4 Mar 2008 11:48:53 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <ak@...e.de>
Cc:	"Huang, Ying" <ying.huang@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: early_res and find_e820_area for i386?

* Andi Kleen <ak@...e.de> wrote:

> On Tuesday 04 March 2008 04:38:03 Huang, Ying wrote:
> 
> > Is it better to implement early_res and find_e820_area on i386? Can 
> > we trust E820 table on i386?
> 
> The 64bit code is certainly more flexible and cleaner, but also much 
> more complicated.. [...]

i disagree, the early_res stuff is still quite unclean, and what we want 
do do is to get rid of it, not promote it into 32-bit code ... (The 
reason we merged the early_res stuff in 2.6.25 was because it was 
certainly cleaner than the horrible open-coded reservations that the 
64-bit code did before. So now we at least have a more less visible 
enumeration of reservations.)

The correct and clean clean solution is what hpa mentioned: to do 
reservations in the e820 space. I think hpa has some code for that 
already and we should merge that. Peter?

	Ingo
--
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/