All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Jan Beulich <jbeulich@novell.com>
Subject: Re: Xen hypervisor hangs on booting against c/s 16925
Date: Tue, 29 Jan 2008 12:22:29 +0000	[thread overview]
Message-ID: <20080129122229.55d3828f@core> (raw)
In-Reply-To: <C3C4B249.1B901%Keir.Fraser@cl.cam.ac.uk>

On Tue, 29 Jan 2008 10:36:57 +0000
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:

> How about we just map the whole megabyte UC- at start of day? We rarely
> touch anything down there and when we do it'll mostly be BIOS tables (hence
> in ROM and hence not marked as RAM in e820 

Most BIOS tables are in RAM because they are built each boot. Mapping the
low 640K UC is also going to suprise the BIOS somewhat and seems to be
asking for trouble.

The MTRR mappings for the low 1Mb are special anyway and aligned with the
need for 640K RAM and a following ISA hole.

Alan

  parent reply	other threads:[~2008-01-29 12:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29  5:58 Xen hypervisor hangs on booting against c/s 16925 Li, Haicheng
2008-01-29  7:40 ` Li, Haicheng
2008-01-29  7:53   ` Keir Fraser
2008-01-29  9:37 ` Keir Fraser
2008-01-29 10:05   ` Jan Beulich
2008-01-29 10:20     ` Keir Fraser
2008-01-29 10:29       ` Christoph Egger
2008-01-29 10:34       ` Jan Beulich
2008-01-29 10:36         ` Keir Fraser
2008-01-29 10:40           ` Keir Fraser
2008-01-29 10:54             ` Jan Beulich
2008-01-29 10:55               ` Keir Fraser
2008-01-29 12:22           ` Alan Cox [this message]
2008-01-29 10:45         ` Keir Fraser
2008-01-29 10:52           ` Jan Beulich
2008-01-29 10:54             ` Keir Fraser
2008-01-29 11:08               ` Jan Beulich
2008-01-29 11:58       ` Alan Cox

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=20080129122229.55d3828f@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=jbeulich@novell.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.