RE: [Xen-devel] pvops-2.6.32 - Interrupt routing problem

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

Could you try the following patch ?  Currently, the GSI 0-15 's polarity and 
trigger mode are determined by hypervisor, and maybe hypervisor and dom0 has no 
agreement to determin them. Just follow dom0's setting with this patch, and I 
think it maybe work for you. 
Xiantao

diff -r 4152a3ce90a7 xen/arch/x86/physdev.c
--- a/xen/arch/x86/physdev.c    Thu Mar 11 17:40:35 2010 +0000
+++ b/xen/arch/x86/physdev.c    Mon Mar 15 12:27:15 2010 +0800
@@ -477,7 +477,7 @@ ret_t do_physdev_op(int cmd, XEN_GUEST_H
         if ( setup_gsi.gsi < 0 || setup_gsi.gsi >= nr_irqs_gsi )
             break;
         /* GSI < 16 has been setup by hypervisor */
-        if ( setup_gsi.gsi >= 16 )
+        if ( setup_gsi.gsi >= 5 )
             ret = mp_register_gsi(setup_gsi.gsi, setup_gsi.triggering,
                             setup_gsi.polarity);
         else


Bastian Blank wrote:
> On Sun, Mar 14, 2010 at 08:56:22AM -0700, Jeremy Fitzhardinge wrote:
>> global because otherwise nothing would work).  It's interesting your
>> devices both have GSIs in the "legacy ISA" range (< 16); I wonder if
>> something somewhere is misdescribing the interrupts.
> 
> Well, they are connected to the first IO-APIC, which only serves 0-15,
> so they can't be bound to other GSI.  But I haven't seem this
> behaviour on any other machine.  Is there a standard that forbids
> this behaviour? 




>> Could you post full boot logs for the kernel booting both native and
>> under Xen to see how they differ?
> 
> Attached.
> 
> Bastian


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