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] HVM windows - PCI IRQ firing on both CPU's

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] HVM windows - PCI IRQ firing on both CPU's
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Mon, 18 Aug 2008 20:53:30 +1000
Delivery-date: Mon, 18 Aug 2008 03:53:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckBIKaFdOX6QU6hSgaQozLRUZxMrQ==
Thread-topic: HVM windows - PCI IRQ firing on both CPU's
I'm just doing some testing on the gplpv drivers with different ways of
handling interrupts, and I'm trying a scheme where each xen device (eg
vbd/vif) driver attaches to the same IRQ as the pci driver, and each
handles it in sequence.

In testing though, I noticed the following when logging what each ISR is

60.32381439 - evtchn event on port 5
60.32384109 - port 5 handler (does some work)
60.32386780 - port 6 handler
60.32389069 - port 7 handler
0.00616564 - evtchn nothing to do
0.00619481 - port 5 handler
0.00621962 - port 6 handler
0.00624393 - port 7 handler

The first number is the timestamp (why is the TSC so far out of whack
between CPU's??? Is that a hardware thing or a Xen thing? It causes huge
problems with 'ping' too!!!), the second is the isr that is running.

Why is the ISR getting run again immediately on the other CPU? Is this
an OS thing or am I not acking the interrupt correctly?



Xen-devel mailing list