This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] vesafb

To: Jan Beulich <jbeulich@xxxxxxxxxx>, Kaushik Barde <Kaushik_Barde@xxxxxxxxxxx>
Subject: Re: [Xen-devel] vesafb
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 09 May 2007 09:14:07 +0100
Cc: ron minnich <rminnich@xxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Jayant Mangalampalli <Jayant_Mangalampalli@xxxxxxxxxxx>
Delivery-date: Wed, 09 May 2007 01:10:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <464198E9.76E4.0078.0@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceSEgONQkBQYv4FEdu9MQAWy6hiGQ==
Thread-topic: [Xen-devel] vesafb
User-agent: Microsoft-Entourage/
On 9/5/07 08:48, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

>> For one thing, there's some extended BIOS data that Linux would like to get
>> its hands on. Another is that it might be nice to get the memory-map
>> information for ourselves instead of relying on the bootloader (there's at
>> least one system we've seen where GRUB gets it wrong). Really there aren't
>> that many examples, and they'd all be invoked at start-of-day.
> ... and for which I had already posted patches to do all that's needed before
> entering C code (and namely, before enabling paging and [on x86-64] long
> mode), almost like Linux does - I have to admit that I continue to favor that
> solution, including extending it to set the VESA mode and, if that's really
> important as you say, calling INT 15 fn E820.

Yes, I have come around to this. It's not so great that we have to export
that EDD structure out to dom0, but it does look to be mostly laid out
according to BIOS specs. And we can't safely run the code which actually
reads disc sectors after we've messed with IRQ setup anyway (assuming some
BIOSes may depend on interrupts and running with EFLAGS.IF==1, although I'm
not sure about this).

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>