From: Gerd Hoffmann <kraxel@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: Re: pv_ops parport trouble
Date: Thu, 19 Feb 2009 16:28:22 +0100 [thread overview]
Message-ID: <499D7A96.4010907@redhat.com> (raw)
In-Reply-To: <499D6EF4.4000801@redhat.com>
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
next prev parent reply other threads:[~2009-02-19 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 14:38 pv_ops parport trouble Gerd Hoffmann
2009-02-19 15:28 ` Gerd Hoffmann [this message]
2009-02-19 16:07 ` Keir Fraser
2009-02-19 16:23 ` Jeremy Fitzhardinge
2009-02-19 16:31 ` Gerd Hoffmann
2009-02-19 16:37 ` Jeremy Fitzhardinge
2009-02-19 16:45 ` Gerd Hoffmann
2009-02-19 16:49 ` Jeremy Fitzhardinge
2009-02-19 16:56 ` Gerd Hoffmann
2009-02-19 17:11 ` Keir Fraser
2009-02-19 16:51 ` Keir Fraser
2009-02-19 17:08 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=499D7A96.4010907@redhat.com \
--to=kraxel@redhat.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.