All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: John Hannfield <hal9020@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: X86_64 and 4GB RAM using Flat Memory Model?
Date: Tue, 01 May 2007 14:15:23 +0100	[thread overview]
Message-ID: <C25CFBFB.E33B%keir@xensource.com> (raw)
In-Reply-To: <4d95b0990705010324if983b91wdcd1a671bbc5b37a@mail.gmail.com>

On 1/5/07 11:24, "John Hannfield" <hal9020@gmail.com> wrote:

> OK, I have updated my grub to the latest available from Debian stable/etch.
> When I access grub at the boot menu, it displays the following for
> 'displaymem'
> 
> grub> displaymem
> EISA Memory BIOS Interface is present
> Address Map BIOS Interface is present
> Lower memory: 631K, Upper memory (to first chipset hole): 3144640K

So the issue here is that grub has for some reason been upset by the values
returned to it by the e820 bios command, and has decided to fall back to a
simpler bios command which only tells you amount of memory up to the first
memory hole. This wouldn't necessarily affect Linux because it interrogates
the bios itself, using different code which isn't affected by this bug
(either it's a bios bug which Linux explicitly works around or is simply not
susceptible to; or it's a grub bug which Linux doesn't have).

> Any further ideas?

It's grim news I'm afraid.

 1. Dig into why GRUB is bailing on the e820 map, and come up with a grub
patch to fix (or work around) the bug. This will require modifying,
building, installing grub, rebooting the machine, etc etc. It's a pain in
the arse.

 2. Boot via a different method (basically that would mean pxe). This might
be convenient or impossible, depending on your machine's local network
environment.

 3. There is no command-line option for overrding the e820 map. We could
lash one up, or I can give you a basic patch for you to fill in the blanks
with your memory map. You can then build special Xen with hardcoded map for
that box.

 -- Keir

> Normal debian etch booting on same machine sees all 4GB, using the same
> grub. But I guess it doesn't get the memory map from grub?  If I know the
> memory
> map from the vanilla linux boot, can I provide this another way to xen?

  reply	other threads:[~2007-05-01 13:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-28 13:14 X86_64 and 4GB RAM using Flat Memory Model? John Hannfield
2007-04-28 13:25 ` Keir Fraser
2007-04-28 13:33   ` John Hannfield
2007-04-28 14:03     ` Keir Fraser
2007-04-28 14:30       ` John Hannfield
2007-04-28 14:35         ` Keir Fraser
2007-04-28 14:39           ` John Hannfield
2007-04-28 15:22             ` Keir Fraser
2007-04-28 15:41               ` John Hannfield
2007-04-29  8:43                 ` Keir Fraser
2007-04-29 10:54                   ` John Hannfield
2007-05-01 10:24               ` John Hannfield
2007-05-01 13:15                 ` Keir Fraser [this message]
2007-05-01 13:27                   ` Keir Fraser
2007-05-01 14:07                   ` John Hannfield
2007-05-02  0:07                     ` James Harper
2007-05-02  6:32                       ` Keir Fraser

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=C25CFBFB.E33B%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=hal9020@gmail.com \
    --cc=xen-devel@lists.xensource.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.