From: Chuck Ebbert <cebbert@redhat.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: Lossy interrupts on x86_64
Date: Fri, 14 Sep 2007 13:35:15 -0400 [thread overview]
Message-ID: <46EAC653.3010603@redhat.com> (raw)
In-Reply-To: <200709120929.52217.jbarnes@virtuousgeek.org>
On 09/12/2007 12:29 PM, Jesse Barnes wrote:
>
> [jbarnes@jbarnes-t61 ~]$ cat /proc/interrupts
> CPU0 CPU1
> 0: 290050 289541 IO-APIC-edge timer
> 1: 3862 3956 IO-APIC-edge i8042
> 8: 0 0 IO-APIC-edge rtc0
> 9: 1632 1643 IO-APIC-fasteoi acpi
> 12: 183662 183926 IO-APIC-edge i8042
> 14: 20626 20717 IO-APIC-edge libata
> 15: 0 0 IO-APIC-edge libata
> 16: 46812 46825 IO-APIC-fasteoi yenta, uhci_hcd:usb3, i915@pci:0000:00:02.0
> 17: 63715 63653 IO-APIC-fasteoi uhci_hcd:usb4, HDA Intel, firewire_ohci, iwl4965
> 18: 0 0 IO-APIC-fasteoi uhci_hcd:usb5
> 19: 52 36 IO-APIC-fasteoi ehci_hcd:usb7
> 20: 43 46 IO-APIC-fasteoi uhci_hcd:usb1
> 21: 0 0 IO-APIC-fasteoi uhci_hcd:usb2
> 22: 2 1 IO-APIC-fasteoi ehci_hcd:usb6
> 2297: 937 944 PCI-MSI-edge eth0
> 2298: 12392 12402 PCI-MSI-edge ahci
> NMI: 0 0
> LOC: 290913 335027
> ERR: 0
>
Hmm, is there any way to force those "fasteoi" handlers to "level"
instead?
next prev parent reply other threads:[~2007-09-14 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 15:33 Lossy interrupts on x86_64 Jesse Barnes
2007-09-12 16:01 ` Randy Dunlap
2007-09-12 16:29 ` Jesse Barnes
2007-09-12 17:06 ` Thomas Gleixner
2007-09-17 19:13 ` Jesse Barnes
2007-09-17 19:18 ` Thomas Gleixner
2007-09-17 19:40 ` Jesse Barnes
2007-09-20 19:22 ` Jesse Barnes
2007-09-20 19:50 ` Thomas Gleixner
2007-09-21 0:40 ` Jesse Barnes
2007-09-14 17:35 ` Chuck Ebbert [this message]
2007-09-13 13:40 ` Chris Snook
2007-09-17 19:24 ` Jesse Barnes
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=46EAC653.3010603@redhat.com \
--to=cebbert@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox