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: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Jan Beulich" <jbeulich@xxxxxxxxxx>
Subject: RE: [Xen-devel] vesafb
From: "Kaushik Barde" <Kaushik_Barde@xxxxxxxxxxx>
Date: Tue, 8 May 2007 14:43:47 -0700
Cc: ron minnich <rminnich@xxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Jayant Mangalampalli <Jayant_Mangalampalli@xxxxxxxxxxx>
Delivery-date: Tue, 08 May 2007 14:42:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C266AB80.7012%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <0EF82802ABAA22479BC1CE8E2F60E8C30179963C@xxxxxxxxxxxxxxxxxxxxxxx> <C266AB80.7012%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceRXRJlUQPl1v1QEduQdAAX8io7RQAQteTAAAMd5McAAB36YAAC9WcfAAAEgTA=
Thread-topic: [Xen-devel] vesafb

Yes, I remember that GRUB bug where the initial memory was incorrectly

As for the e820 and EBDA, you need them only at machine boot-up.


-----Original Message-----
From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
Sent: Tuesday, May 08, 2007 2:35 PM
To: Kaushik Barde; Jan Beulich
Cc: ron minnich; Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxx; Jayant
Subject: Re: [Xen-devel] vesafb

On 8/5/07 21:47, "Kaushik Barde" <Kaushik_Barde@xxxxxxxxxxx> wrote:

> <<However, doing one or two calls back to real mode before
>  dom0 even starts to execute should definitely not be a problem
> Ok.. We will test this solution.
> I am curious,
> Why else would you be jumping into real mode after/before the Dom0
> creation?

For one thing, there's some extended BIOS data that Linux would like to
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
least one system we've seen where GRUB gets it wrong). Really there
that many examples, and they'd all be invoked at start-of-day.

 -- Keir

Xen-devel mailing list

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