WARNING - OLD ARCHIVES

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

xen-devel

RE: [Xen-devel] HVM windows - PCI IRQ firing on both CPU's

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] HVM windows - PCI IRQ firing on both CPU's
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Mon, 18 Aug 2008 22:19:01 +1000
Cc:
Delivery-date: Mon, 18 Aug 2008 05:19:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C4CF2469.26172%keir.fraser@xxxxxxxxxxxxx>
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>
References: <AEC6C66638C05B468B556EA548C1A77D0149032F@trantor> <C4CF2469.26172%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckBIKaFdOX6QU6hSgaQozLRUZxMrQACj3ysAABk+0A=
Thread-topic: [Xen-devel] HVM windows - PCI IRQ firing on both CPU's
> On 18/8/08 11:53, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> > 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?
> 
> You should be checking and clearing only vcpu0's evtchn_upcall_pending
and
> evtchn_pending_sel fields. Other vcpu's equivalent fields are
currently
> unused for HVM guests. It is essential that you clear
> evtchn_upcall_pending
> -- that is the 'virtual interrupt wire' connected to the virtual PIC's
> level-triggered input pin.

Just so I understand, even if I see the IRQ on CPU1, I should always
treat it as if it came in on CPU0?

The lack of that would explain what I'm seeing.

Thanks

James 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel