RE: [Xen-devel] Re: APIC rework

["Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>]

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. 

Xiantao


Keir Fraser wrote:
> On 13/11/2009 23:57, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx> wrote:
> 
>>> Sure, I'll check it in.
>>> 
>> 
>> How would you feel about backporting this into a stable release?  If
>> we start using this interrupt setup mechanism it will be a
>> red-letter day for dom0/xen compatibility.
> 
> There probably won't be another stable release until 4.0 now. There
> will be a 3.4.3 about the same time though.
> 
>  -- Keir

Attachment: 0001-x86-Introduce-a-bit-MAP_COMPAT-mode-for-MAP_PIRQ_TY.patch
Description: 0001-x86-Introduce-a-bit-MAP_COMPAT-mode-for-MAP_PIRQ_TY.patch

Attachment: xen-introduce-a-bit-to-identify-dom0-type.patch
Description: xen-introduce-a-bit-to-identify-dom0-type.patch

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