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

[Xen-devel] wait_on_xen_event_channel

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] wait_on_xen_event_channel
From: "Ky Srinivasan" <ksrinivasan@xxxxxxxxxx>
Date: Wed, 07 Mar 2007 16:34:36 -0700
Delivery-date: Wed, 07 Mar 2007 15:33:53 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
Why does this macro take port as an argument? It does not look like the port 
argument is used in the macro.  I want to implement a blocking synchronization  
primitive in the hypervisor where the invoking vcpu will relinquish the CPU; 
and the execution would resume out of the blocking primitive when the vcpu is 
"woken up". The 



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

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