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


RE: [Xen-devel] [RFC] Pass-through Interdomain Interrupts Sharing (HVM/D

To: "Keir Fraser" <keir@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [RFC] Pass-through Interdomain Interrupts Sharing (HVM/Dom0)
From: "Guy Zana" <guy@xxxxxxxxxxxx>
Date: Fri, 10 Aug 2007 06:22:06 -0400
Cc: Alex Novik <alex@xxxxxxxxxxxx>
Delivery-date: Fri, 10 Aug 2007 03:30:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2E1CCA2.C5D1%keir@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/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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfarSF45lhECFFTQSiE3oBAG7IKmQAbyytWAAAcBIUABr4MgA==
Thread-topic: [Xen-devel] [RFC] Pass-through Interdomain Interrupts Sharing (HVM/Dom0)

> -----Original Message-----
> From: Keir Fraser [mailto:keir@xxxxxxxxxxxxx] 
> Sent: Friday, August 10, 2007 10:05 AM
> To: Guy Zana; xen-devel@xxxxxxxxxxxxxxxxxxx
> Cc: Alex Novik
> Subject: Re: [Xen-devel] [RFC] Pass-through Interdomain 
> Interrupts Sharing (HVM/Dom0)
> My thought here is a simple priority list with move-to-back 
> of the frontmost domain when we deliver him the interrupt but 
> he does not deassert the line either in reasonable time or by 
> the time he EOIs the interrupt. This is simple generic logic 
> needing no PV guest changes.

Even if the HVM handled the interrupt successfully, it doesn't mean that the 
pline will be deasserted (if another device assigned to another domain asserted 
it while the HVM processed the interrupt).You can't tell whether the HVM 
handled the interrupt successfully or not. How this method overcome this?

Btw, with the method we proposed you could add PV domains to the interdomain 
ISR chain, but it may not contain more than one HVM.


Xen-devel mailing list

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