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/
Home Products Support Community News


[Xen-devel] Re: [PATCH][FIX] Possible fix for spurious interrupts

To: "Stephen C. Tweedie" <sct@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH][FIX] Possible fix for spurious interrupts
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 14 Apr 2006 09:54:29 +0100
Cc: Michele <vo.sinh@xxxxxxxxx>, xen-devel Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Fri, 14 Apr 2006 01:58:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1144958375.3422.31.camel@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <d5bbd21c73db9bb960c3b63a90d24ec2@xxxxxxxxxxxx> <1144958375.3422.31.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 13 Apr 2006, at 20:59, Stephen C. Tweedie wrote:

Looks like it cures it completely for me. I've got the same box running
the same load that used to send irq16 through the roof, and it's
currently pegged at:

         16:  0   0   0   0  Phys-irq  uhci_hcd:usb2, uhci_hcd:usb5


Actually, it seems the patch doesn't entirely work for multi-processor domain 0 as the wrong local APIC is sometimes prodded to do the EOI cycle. This was partially hidden by the fact that IRQ ffinity is also currently broken in our Linux tree (we need to call move_irq() in a few choice places). I'll get a complete fix for all this stuff into xen-unstable today. Probably the meat of the patch should wait a while before going into the -testing tree, but we'll want to get something in there before 3.0.2-3.

 -- Keir

Xen-devel mailing list