From: "Huang, Ying" <ying.huang@intel.com>
To: Paul Jackson <pj@sgi.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Bernhard Walle <bwalle@suse.de>,
Johannes Weiner <hannes@saeurebad.de>,
linux-kernel@vger.kernel.org, Jack Steiner <steiner@sgi.com>
Subject: Re: Confusions with reserve_early, reserve_bootmem, e820, efi, ... on x86_64
Date: Fri, 13 Jun 2008 08:59:39 +0800 [thread overview]
Message-ID: <1213318779.20431.3.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <20080612050609.88a8cf7f.pj@sgi.com>
On Thu, 2008-06-12 at 05:06 -0500, Paul Jackson wrote:
> Bernhard, Johannes, Huang, and Yinghai:
>
> I am running into some complications with reserve_bootmem vs
> reserve_early, and a reserve_early of "EFI memmap" in the
> efi_reserve_early() routine conflicting with reserve_early of
> "BIOS reserved" in reserve_ebda_region().
>
> This is on x86_64 arch, using Ingo's x86-latest, with possibly
> still buggy EFI firmware in a lab system I'm helping to develop.
>
> I have three concerns:
>
> 1) The find_overlapped_early() check called from reserve_early is
> failing on my lab system , causing panic, when it tries to
> register "EFI memmap" at addresses <0xe0660, 0xe0778> that
> overlaps with the "BIOS reserved" early reserve at addresses
> <0x9f000, 0x100000>
I think this can be resolved by avoiding memory area <0x9f000, 0x100000>
when allocating memory for EFI memory map in boot-loader.
Best Regards,
Huang Ying
prev parent reply other threads:[~2008-06-13 0:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 10:06 Confusions with reserve_early, reserve_bootmem, e820, efi, ... on x86_64 Paul Jackson
2008-06-12 12:25 ` Yinghai Lu
2008-06-12 16:19 ` Paul Jackson
2008-06-12 17:05 ` Yinghai Lu
2008-06-12 20:10 ` Paul Jackson
2008-06-12 20:29 ` Yinghai Lu
2008-06-12 21:09 ` H. Peter Anvin
2008-06-12 21:52 ` Paul Jackson
2008-06-12 22:06 ` Yinghai Lu
2008-06-12 22:13 ` Paul Jackson
2008-06-12 22:39 ` H. Peter Anvin
2008-06-13 0:59 ` Huang, Ying [this message]
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=1213318779.20431.3.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=bwalle@suse.de \
--cc=hannes@saeurebad.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pj@sgi.com \
--cc=steiner@sgi.com \
--cc=yhlu.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.