public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@suse.de>
Cc: "Huang, Ying" <ying.huang@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: early_res and find_e820_area for i386?
Date: Tue, 4 Mar 2008 11:48:53 +0100	[thread overview]
Message-ID: <20080304104853.GA19022@elte.hu> (raw)
In-Reply-To: <200803041141.28404.ak@suse.de>


* Andi Kleen <ak@suse.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

  reply	other threads:[~2008-03-04 10:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04  3:38 early_res and find_e820_area for i386? Huang, Ying
2008-03-04  4:23 ` H. Peter Anvin
2008-03-04 10:34   ` Ingo Molnar
2008-03-04 10:41 ` Andi Kleen
2008-03-04 10:48   ` Ingo Molnar [this message]
2008-03-04 11:46     ` Andi Kleen
2008-03-04 16:31     ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080304104853.GA19022@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox