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]

Date:	Tue, 4 Mar 2008 12:46:47 +0100
From:	Andi Kleen <ak@...e.de>
To:	Ingo Molnar <mingo@...e.hu>
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?

On Tuesday 04 March 2008 11:48:53 Ingo Molnar wrote:
> 
> * 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, 

I was mostly refering to the main e820 allocator.

early_res is just an addon table for kernel internal use. While you
could put that into the main e820 table too if you made that one variable
sized I don't think it would make too much difference either way. 
It's just a minor tweak of the data structure.

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