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: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: RE: [Xen-devel] Re: APIC rework
From: "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
Date: Tue, 17 Nov 2009 11:13:14 +0800
Accept-language: en-US
Acceptlanguage: en-US
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 19:14:11 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B019C00.2070404@xxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acpm6+sjvDcxUGwNQduO6bITFGn2LwAR5CTA
Thread-topic: [Xen-devel] Re: APIC rework
Jeremy Fitzhardinge wrote:
> On 11/16/09 02:38, Zhang, Xiantao wrote:
>> Hi, Keir/Jeremy
>>    After you picking the two patches into upstream, we found it may
>> break old dom0 when assigned a level-triggered devices to a HVM
>> domain.  The casue is that, old dom0 can't provide trigger mode and
>> polarity when they do map_domain_pirq.  In attached patches, they
>> introduce a bit to indicate whether old dom0 or not.    
>> xen-introduce-a-bit-to-identify-dom0-type.patch:  for hypervisor.
>> 0001-x86-Introduce-a-bit-MAP_COMPAT-mode-for-MAP_PIRQ_TY.patch: for
>> pv ops dom0. 
> 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.  
Xen-devel mailing list

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