Date: Tue, 4 Mar 2008 11:34:48 +0100
From: Ingo Molnar <mingo@elte.hu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Huang, Ying" <ying.huang@intel.com>, Ingo Molnar <mingo@redhat.com>,
       Thomas Gleixner <tglx@linutronix.de>, Andi Kleen <ak@suse.de>,
       linux-kernel@vger.kernel.org
Subject: Re: early_res and find_e820_area for i386?
Message-ID: <20080304103448.GC17621@elte.hu>
References: <1204601883.4707.96.camel@caritas-dev.intel.com> <47CCCED4.30607@zytor.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47CCCED4.30607@zytor.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 740
Lines: 21


* H. Peter Anvin <hpa@zytor.com> wrote:

>> BTW: Why not merge e820_32.c and e820_64.c? At least part of them.
>
> What we *should* do, on both i386 and x86-64, is to create a synthetic 
> e820 table of any non-e820 information, and then yes, we should merge 
> the code.
>
> In other words, we should have an e820 table which reflects what the 
> kernel considers true about the memory space.

i'd strongly support the moving of this from the realm of talk into the 
realm of code! :-)

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