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] APIC handling on x86-64

To: <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] APIC handling on x86-64
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Mon, 20 Mar 2006 14:53:53 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 20 Mar 2006 13:55:11 +0000
Envelope-to: www-data@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
>Yes, that's what stopped me taking x86/64 Linux code originally. I 
>wonder if we can take just the IPI code from x86/64, plus whatever 
>small changes we need to fix problems like this x460 bug. IPI code is 
>reasonably self contained relative to the bulk of the apic code in 
>apic.c. The x86/64 IPI code was a bunch cleaner than the i386 code last 
>time I looked, and I don't think there are lurking legacy 32-bit issues 
>in that area that would bite us?

Hmm, I'm not sure. Both because it wouldn't address all issues (the
I/O APIC redirection table entries also need to be programmed in
physical mode) and because I'm not so certain about legacy 32-bit
issues (on 32-bits you still have to account for the PentiumPro/II/III
behavior, namely the only 4-bit wide IDs, as that at least seems to
imply different cut-off criteria for the decision what destination mode
to use).

Jan

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