Re: Lossy interrupts on x86_64

From: Chuck Ebbert
Date: Fri Sep 14 2007 - 13:36:21 EST


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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/