From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: pv_ops parport trouble
Date: Thu, 19 Feb 2009 16:28:22 +0100
Message-ID: <499D7A96.4010907@redhat.com>
References: <499D6EF4.4000801@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <499D6EF4.4000801@redhat.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jeremy Fitzhardinge <jeremy@goop.org>, Xen Development Mailing List <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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