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

[Xen-devel] Re: pv_ops parport trouble

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: pv_ops parport trouble
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: Thu, 19 Feb 2009 16:28:22 +0100
Cc:
Delivery-date: Thu, 19 Feb 2009 07:28:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <499D6EF4.4000801@xxxxxxxxxx>
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: <499D6EF4.4000801@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.19 (X11/20090105)
Gerd Hoffmann wrote:
>   Hi,
> 
> I see on my test box _excessive_ irqs for parport0:
> 
> [root@xeni ~]# cat /proc/interrupts
>            CPU0
> [ ... ]
>   7:   37316845  xen-pirq-pirq      parport0
> [ ... ]
>  24:      17698   xen-dyn-virq      timer0
> [ ... ]
> 
> Something is seriously wrong here ...

More info:

[root@xeni ~]# cat /proc/interrupts
           CPU0
  1:          0  xen-pirq-pirq      i8042
  3:         13  xen-pirq-pirq
  4:         17  xen-pirq-pirq
  7:   17797333  xen-pirq-pirq      parport0
  8:          1  xen-pirq-pirq      rtc0
  9:          0  xen-pirq-pirq      acpi
 16:          0  xen-pirq-pirq      uhci_hcd:usb3, uhci_hcd:usb8
 18:          0  xen-pirq-pirq      uhci_hcd:usb5
 19:      14697  xen-pirq-pirq      ehci_hcd:usb1, uhci_hcd:usb7, ahci
 20:       5142  xen-pirq-pirq      eth0
 21:          0  xen-pirq-pirq      uhci_hcd:usb4
 22:        240  xen-pirq-pirq      HDA Intel
 23:          0  xen-pirq-pirq      ehci_hcd:usb2, uhci_hcd:usb6

(XEN) Guest interrupt information:
(XEN)     IRQ  1 Vec 40: type=IO-APIC-edge    status=00000010
in-flight=0 domain-list=0(-S--),
(XEN)     IRQ  7 Vec 80: type=IO-APIC-level   status=00000010
in-flight=1 domain-list=0(PS-M),
(XEN)     IRQ  8 Vec 88: type=IO-APIC-level   status=00000010
in-flight=0 domain-list=0(-S--),
(XEN)     IRQ  9 Vec 96: type=IO-APIC-level   status=00000010
in-flight=0 domain-list=0(-S--),
(XEN)     IRQ 16 Vec 33: type=IO-APIC-edge    status=00000010
in-flight=0 domain-list=0(-S--),
(XEN)     IRQ 18 Vec 49: type=IO-APIC-edge    status=00000010
in-flight=0 domain-list=0(-S--),
(XEN)     IRQ 19 Vec208: type=IO-APIC-edge    status=00000010
in-flight=0 domain-list=0(-S--),
(XEN)     IRQ 20 Vec 57: type=IO-APIC-edge    status=00000010
in-flight=0 domain-list=0(-S--),
(XEN)     IRQ 21 Vec 41: type=IO-APIC-edge    status=00000010
in-flight=0 domain-list=0(-S--),
(XEN)     IRQ 22 Vec 65: type=IO-APIC-edge    status=00000010
in-flight=0 domain-list=0(-S--),
(XEN)     IRQ 23 Vec216: type=IO-APIC-edge    status=00000010
in-flight=0 domain-list=0(-S--),

Note that IRQ 7 is *level* triggered and we have a bunch of *shared*
irqs which are *edge* triggered.  Given this I wonder my test box is
able to stay up that long.

cheers,
  Gerd

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