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

Re: [Xen-devel] [RFC] Genapic in x86_64 Dom0

To: Chris Wright <chrisw@xxxxxxxx>
Subject: Re: [Xen-devel] [RFC] Genapic in x86_64 Dom0
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 22 Aug 2005 19:48:24 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Delivery-date: Mon, 22 Aug 2005 18:46:35 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Your message of "Mon, 22 Aug 2005 11:20:36 PDT." <20050822182036.GV7762@xxxxxxxxxxxxxxxxxxx>
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
> * Keir Fraser (Keir.Fraser@xxxxxxxxxxxx) wrote:
> > Perhaps genapic_xen is currently being too smart for its own good? :-)
> 
> Hehe, quite possible ;-)
> 
> > On i386 we lobotomised local apic handling.
> 
> My goal was to avoid (equivalent of) #if 0 where possible, by backfilling
> functionality where possible.  I also had filled out mpc_config_processor
> during mp_register_lapic and tried to maintain the physid map (that bit
> isn't merged).  Do you think there's value in maintaining that level of
> code compatibility?

I suspect we might be best off just diverging completely and having
our own file that implements enough of the local APIC "interface" to
get everything else to build, but is basically a set of no-ops. That's
basically what we have for arch/xen/i386.

Maintaining processor and lapic info is pretty pointless since those
things aren't under domain 0's control, although it may be as easy to
do so as not. 

 -- Keir

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

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