public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: 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?
Date: Mon, 03 Mar 2008 20:23:48 -0800	[thread overview]
Message-ID: <47CCCED4.30607@zytor.com> (raw)
In-Reply-To: <1204601883.4707.96.camel@caritas-dev.intel.com>

Huang, Ying wrote:
> Hi,
> 
> Before bootmem allocator is available, kernel needs allocate memory
> pages such as page table and some NUMA structures. On x86_64, this is
> done by early_res and find_e820_area. On i386, this is done through
> using the memory area after kernel itself which is tracked with
> init_pg_tables_end.
> 
> Is it better to implement early_res and find_e820_area on i386? Can we
> trust E820 table on i386?
> 
> Or we add an early_alloc, which allocate memory from the memory area
> after kernel itself and check the early_res areas and E820 table too.
> 
> 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.

	-hpa

  reply	other threads:[~2008-03-04  4:24 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 [this message]
2008-03-04 10:34   ` Ingo Molnar
2008-03-04 10:41 ` Andi Kleen
2008-03-04 10:48   ` Ingo Molnar
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=47CCCED4.30607@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@suse.de \
    --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