From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH 2/3] x86: real mode support: get EDD info Date: Fri, 02 Mar 2007 11:15:44 +0000 Message-ID: References: <45E80B3F.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45E80B3F.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 2/3/07 10:32, "Jan Beulich" 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? 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). -- Keir