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] Interrupt synchronisation and HVM

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Interrupt synchronisation and HVM
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Fri, 25 Jul 2008 17:02:03 +1000
Cc:
Delivery-date: Fri, 25 Jul 2008 00:02:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C4AF3792.1B8D1%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: <AEC6C66638C05B468B556EA548C1A77D01490021@trantor> <C4AF3792.1B8D1%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjuGCB1rA6bC/FxTNi4IWNnmz7YQwAC1+cNAAAIUmA=
Thread-topic: [Xen-devel] Interrupt synchronisation and HVM
> 
> The evtchn_upcall_mask is not respected for HVM guests. When you set
> HVM_PARAM_CALLBACK_IRQ to 0, no more interrupts will be generated at
the
> PIC or IO-APIC. But any interrupts queued up at either of those will
> eventually get propagated to the CPU.

Thanks. I wish I'd known that earlier :|

> Is there a way to de-register from an IRQ and
> hence get Windows to mask the PIC/IO-APIC line?

Yes, I was doing that previously but under Windows you can only register
and unregister an interrupt at PASSIVE_LEVEL (all interrupts and thread
switching enabled), which I didn't want to do as when I disable
interrupts for a save/suspend, I don't want windows doing that sort of
thing (eg trying to perform a paging operation or something).

I've worked around it for now by just flipping a flag to say to the ISR
to just return if it gets an interrupt after a certain point.
Save/restore suddenly seems to work perfectly!

Just to clarify, if I have masked the interrupts via
HVM_PARAM_CALLBACK_IRQ = 0, it is safe to do nothing when the interrupt
occurs right? I don't need to unset the 'pending' bits or anything?

Thanks

James

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

<Prev in Thread] Current Thread [Next in Thread>