From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <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 11:58:20 +0000 [thread overview]
Message-ID: <20080129115820.0b97573d@core> (raw)
In-Reply-To: <C3C4AE68.1B8DE%Keir.Fraser@cl.cam.ac.uk>
On Tue, 29 Jan 2008 10:20:24 +0000
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
> Isn't the memory map below 1MB well known, and no I/O exists down there
> except for VGA? Below that is conventional RAM; above that is ROM space.
Low 640K RAM
Above that ISA hole
Above that ROM (often shadowed into RAM)
Of the 640K RAM the low page is owned by the BIOS as are pages above the
EBDA. Some systems also use a 1 page EBDA to hide hardware bugs with
DMA prefetches running off the end of the 640K of RAM into I/O space.
The E820 map then tells you which bits of the 640K are owned by the BIOS
ACPI layer.
The ISA window is all non-cachable device mmio but rarely used for
anything but the PCI routed legacy VGA and MDA.
Alan
prev parent reply other threads:[~2008-01-29 11:58 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
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 [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=20080129115820.0b97573d@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.