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] Re: APIC rework

To: "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: APIC rework
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Mon, 16 Nov 2009 21:12:58 -0800
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Han, Weidong" <weidong.han@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Mon, 16 Nov 2009 21:13:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <706158FABBBA044BAD4FE898A02E4BC201CD320368@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4AFDF254.7070407@xxxxxxxx> <C724151D.1A1B4%keir.fraser@xxxxxxxxxxxxx> <706158FABBBA044BAD4FE898A02E4BC201CD3201A3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B019C00.2070404@xxxxxxxx> <706158FABBBA044BAD4FE898A02E4BC201CD320368@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4
On 11/16/09 19:13, Zhang, Xiantao wrote:
> Jeremy Fitzhardinge wrote:
>> Is there any way for the dom0 kernel to tell whether the hypervisor is
>> implementing the new ABI, so it can choose how to set up interrupts.
>> MAP_COMPAT_BIT doesn't seem like a very good name, because it implies
>> that setting it reverts to "compatible" behaviour.  I assume that
>> leaving it clear enables the historical behaviour and setting it
>> enables the new one (since old kernels won't be setting it).
> Maybe better change to MAP_NEW_ABI_BIT ?  Since the hypervisor patch didn't 
> change old code path after introducing this bit, so it is very easy and safe 
> to backport to xen-3.4-testing tree, and make new dom0 be able to run top of 
> it.  :)

Better to give it a name which actually describes what it means/does. 
NEW_ABI isn't very descriptive when it becomes *the* ABI (and what
happens when there's a newer one?).

> Xiantao

Xen-devel mailing list

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