From: "Huang, Ying" <ying.huang@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
andi@firstfloor.org, mingo@redhat.com, tglx@linutronix.de,
Paul Jackson <pj@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 0/4] x86_64 boot: Add linked listof struct setup_data to boot protocol
Date: Thu, 27 Mar 2008 17:25:36 +0800 [thread overview]
Message-ID: <1206609936.13404.0.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <20080327083221.GD15626@elte.hu>
On Thu, 2008-03-27 at 09:32 +0100, Ingo Molnar wrote:
> * Huang, Ying <ying.huang@intel.com> wrote:
>
> > This patchset adds the linked list of struct setup_data to boot
> > protocol. This is needed by EDD information and some SGI machine with
> > E820 entry number > 128.
>
> what happens with the SGI machine - does it crash (because we overflow
> the e820 array) - or does it boot up with less memory available and we
> get this bootup warning:
>
> Ooops! Too many entries in the memory map!
SGI guys want to build machine with NUMA node number > 128, so they need
e820 entry number > 128. In current boot protocol, this can not be
passed by boot loader to kernel. So the boot protocol need to be
extended.
> ?
>
> I guess we should we raise E820MAX from 128 to 256 (patch below), but if
> we do something worse (crash), we should fix that side-effect as well.
Because the size of "zero page" is limited to 4k, the entry number of
E820 table in "zero page" is limited too. We can not raise it to 256,
because 20 * 256 = 5120 > 4096.
> > Now, only the x86_64 is supported. The i386 can be supported after
> > early reservation mechanism for x86 is available.
>
> could you try to do that nevertheless? We generally prefer feature
> patches after sensible unification has been done.
I try to port reserve_early() to i386 before. But it is said that the
reserve_early() should be replaced by e820 based early
reservation/allocation mechanism on i386 and x86_64. So I think I should
wait for it.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2008-03-27 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 7:09 [PATCH -mm 0/4] x86_64 boot: Add linked listof struct setup_data to boot protocol Huang, Ying
2008-03-27 8:32 ` Ingo Molnar
2008-03-27 9:02 ` Paul Jackson
2008-03-27 9:09 ` Ingo Molnar
2008-03-27 9:21 ` Paul Jackson
2008-03-27 9:46 ` Ingo Molnar
2008-03-27 9:25 ` Huang, Ying [this message]
2008-03-27 9:47 ` Ingo Molnar
2008-03-27 16:36 ` 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=1206609936.13404.0.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=pj@sgi.com \
--cc=tglx@linutronix.de \
/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