WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] early_cpu_init() and identify_cpu()

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] early_cpu_init() and identify_cpu()
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Fri, 13 Jul 2007 17:16:13 +0100
Delivery-date: Fri, 13 Jul 2007 09:12:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
Is there any reason (other than having things inherited this way from Linux) 
that
we cannot call identify_cpu() for the boot CPU at the end of early_cpu_init()
rather than explicitly from __start_xen()? And if not, it would seem reasonable
to me to at once move the two CR4 twiddling pieces out of __start_xen, too.

(I'm not asking because I want to beautify the code, but because I want the
identify to happen earlier, namely I want to fully set up the VESA console as
early as possible, but there I'd like to be able to set MTRRs, which in turn
depends on identify_cpu() having executed.

Thanks, Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel