From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>
Subject: Re: [PATCH 2/3] x86: real mode support: get EDD info
Date: Fri, 02 Mar 2007 11:26:10 +0000 [thread overview]
Message-ID: <45E817E2.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C20DB7E0.A7AD%keir@xensource.com>
>>> Keir Fraser <keir@xensource.com> 02.03.07 12:15 >>>
>On 2/3/07 10:32, "Jan Beulich" <jbeulich@novell.com> wrote:
>
>> Obtain EDD info from BIOS and pass it up to Dom0.
>
>What data format are the EDD/EDID buffers filled with? The format is not
>defined in the public headers. Is it simply whatever Linux happens to be
>using internally?
No, this is the BIOS format. Linux uses this directly. I specifically (based
on past comment from you) avoided introducing Linux specifics.
>I am still interested in trying out an interface to let dom0 request code to
>be run in various modes and on various CPUs. This would be attractive in
>this case, assuming that these BIOS calls could be made later than very
>early bootstrap, as it would avoid piling code into Xen, and assumptions
>about info data formats, just because of the environment that the
>interrogating code needs to be executed in. No doubt it is a larger initial
>amount of engineering effort up front though. Also I'm not sure if there
>would be any subtle gotchas to running this skanky BIOS code later in the
>boot sequence (I'd be optimistic that it'd just work though).
Possible, but especially on x86-64 undesirable in my opinion. Also, I'll want
the base real mode stuff in anyway (regardless of EDD/EDID) in order to
be able to set up a VESA frame buffer mode for the console. This clearly
should be done by Xen in order to ensure it knows how to access the
console in case it is allowed access past dom0 creation.
Jan
next prev parent reply other threads:[~2007-03-02 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 10:32 [PATCH 2/3] x86: real mode support: get EDD info Jan Beulich
2007-03-02 11:15 ` Keir Fraser
2007-03-02 11:26 ` Jan Beulich [this message]
2007-03-02 11:35 ` Keir Fraser
2007-03-02 11:49 ` Petersson, Mats
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=45E817E2.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=keir@xensource.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.