From: "Huang, Ying" <ying.huang@intel.com>
To: Paul Jackson <pj@sgi.com>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
hpa@zytor.com, ak@suse.de, adaplas@pol.net,
linux-kernel@vger.kernel.org
Subject: Re: Could you please merge the x86_64 EFI boot support patchset?
Date: Wed, 23 Jan 2008 16:07:55 +0800 [thread overview]
Message-ID: <1201075675.4945.44.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <20080123014653.6261020c.pj@sgi.com>
On Wed, 2008-01-23 at 01:46 -0600, Paul Jackson wrote:
> Huang wrote:
> > This patchset has been merged into Linux 2.6.24.
>
> Excellent.
>
> > Unfortunately, the new EFI support patches do not use EFI memory map for
> > system boot up ... So, I think the resolution for your problem is the
> > "struct setup_data" mechanism proposed by H. Peter Anvin.
>
> So you're saying that the EFI in the kernel now still won't support more
> than 128 or so chunks of memory in the boottime memory map, because it
> still goes via the legacy E820h memory map code?
The kernel with EFI support can not support more than 128 or so chunks
of memory. Because the EFI memory map is converted to E820 memory map in
boot-loader (such as elilo).
> I'll have to study the code more and give it a try.
>
> Are you optimistic that some variation of H. Peter Anvin's "struct
> setup_data" mechanism will make it into 2.6.25 or thereabouts?
I think it may be merged into 2.6.26.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2008-01-23 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 1:45 Could you please merge the x86_64 EFI boot support patchset? Huang, Ying
2008-01-23 7:00 ` Paul Jackson
2008-01-23 7:26 ` Huang, Ying
2008-01-23 7:46 ` Paul Jackson
2008-01-23 8:07 ` Huang, Ying [this message]
2008-01-23 17:38 ` Paul Jackson
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=1201075675.4945.44.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=adaplas@pol.net \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=torvalds@linux-foundation.org \
/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