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] virtual interrupt from one domain to another

To: "Agarwal, Lomesh" <lomesh.agarwal@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] virtual interrupt from one domain to another
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Mon, 22 Oct 2007 17:20:24 +0800
Delivery-date: Mon, 22 Oct 2007 02:21:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <A3258B497F1C1441AD36A2E8B45FD628D7493B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <A3258B497F1C1441AD36A2E8B45FD628D7493B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgUXfMu0r8PeI55TAiUBsui+xg0ygALeWJg
Thread-topic: [Xen-devel] virtual interrupt from one domain to another
>From: Agarwal,Lomesh
>Sent: 2007年10月22日 11:45
>
>Is there a way to send interrupt from one domain to another? I have
>FE/BE pair in different domains and I want to notify them using
>interrupt. how can I do that? is there a way which most of the FE/BE
>pair generally use?
>

Any reason that existing inter-vm event channel can't satisfy your FE/BE 
pair? On Xen PV 'processor', 'event port' is the basic async notification 
mechanism and even 'interrupt' (in native context) is carried by an event 
port. On Xen HVM 'processor', 'interrupt' is still the basic notification and 
all the 'event ports' are aggregated into one interrupt line derived from a 
dummy PCI device.

But when referring to FE/BE context, inter-vm event channel is always 
the way used by all existing FE/BE drivers.

Thanks,
Kevin

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

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