From: "H. Peter Anvin" <hpa@zytor.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Ben Hutchings <ben@decadent.org.uk>,
x86@kernel.org, 584846@bugs.debian.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bug#584846: Detects only 64MB and fails to boot on Intel Green City board if e820 hooked by GRUB2
Date: Sat, 12 Jun 2010 16:02:44 -0700 [thread overview]
Message-ID: <4C141214.5050601@zytor.com> (raw)
In-Reply-To: <20100612222634.GA1785@feather>
On 06/12/2010 03:26 PM, Josh Triplett wrote:
>
> Everything looks identical except for the region GRUB hooked right below
> the first reserved region; the unhooked version has available memory
> from 0-0x9cbf0, and the hooked version has available memory from
> 0-0x9cba0, then reserved from 0x9cba0-0x9cbec, then 4 bytes of available
> memory, and then the same reserved region as before.
>
Actually... are both these done by chainloading Grub (with and without
mapping), or is the unhooked done without chainloading Grub at all?
To me it looks like something is chaining INT 15h even in the
"unchained" case...
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-06-12 23:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100612060322.29053.94187.reportbug@feather>
2010-06-12 13:58 ` Bug#584846: Detects only 64MB and fails to boot on Intel Green City board if e820 hooked by GRUB2 Ben Hutchings
2010-06-12 18:28 ` H. Peter Anvin
2010-06-12 18:55 ` Josh Triplett
2010-06-12 20:41 ` H. Peter Anvin
2010-06-12 21:45 ` Josh Triplett
[not found] ` <20100612222634.GA1785@feather>
2010-06-12 23:01 ` H. Peter Anvin
2010-06-12 23:02 ` H. Peter Anvin [this message]
2010-06-13 0:07 ` Josh Triplett
2010-06-13 0:16 ` H. Peter Anvin
[not found] ` <20100622052236.GA9130@feather>
2010-06-22 6:07 ` H. Peter Anvin
2010-06-22 16:07 ` Josh Triplett
2010-06-24 7:27 ` Josh Triplett
2010-06-24 14:18 ` H. Peter Anvin
2010-06-24 19:01 ` Josh Triplett
2010-06-24 20:58 ` 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=4C141214.5050601@zytor.com \
--to=hpa@zytor.com \
--cc=584846@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).