From: Guillaume Thouvenin <guillaume.thouvenin@ext.bull.net>
To: Xen devel ML <xen-devel@lists.xensource.com>
Subject: [RFC] change provided physical RAM map to add EBDA
Date: Wed, 14 Mar 2007 11:02:38 +0000 [thread overview]
Message-ID: <20070314110238.GA27518@bull.net> (raw)
Hello
When dom0 starts, we can see that Xen is provided a uniform pseudo physical
RAM map. For example for a dom0 with 1GB of RAM we can see:
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000040800000 (usable)
If I need to use data provided by EBDA, is it possible to change how Xen
provides information to dom0? My idea was to provide something like this:
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000000099000 (usable)
Xen: 0000000000099000 - 00000000000a0000 (reserved for EBDA)
Xen: 00000000000a0000 - 0000000040800000 (usable)
where memory from 99000 to a0000 is a direct mapping to machine address. By
doing this, dom0 will be able to access the extended BIOS data area. This will
allow to port pieces of code that are using EBDA area. I'm thinking about
MP-table parsing routines found in arch/i386/kernel/mpparse.c or IBM summit
code found in arch/i386/kernel/summit.c. Also we can see in
arch/x86_64/kernel/setup-xen.c that currently the code that deals with ebda
is just removed.
Does it make sense to add support for EBDA in dom0 by changing the physical map?
If not, what is the more appropriate solution to get information found in EBDA area
from dom0?
Regards,
Guillaume
next reply other threads:[~2007-03-14 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 11:02 Guillaume Thouvenin [this message]
2007-03-14 12:25 ` [RFC] change provided physical RAM map to add EBDA Ian Campbell
2007-03-15 8:45 ` Guillaume Thouvenin
2007-03-15 9:24 ` Ian Campbell
2007-03-15 10:55 ` Keir Fraser
2007-03-16 7:50 ` Guillaume Thouvenin
2007-03-15 11:57 ` 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=20070314110238.GA27518@bull.net \
--to=guillaume.thouvenin@ext.bull.net \
--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.