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] Event Channel Semantics

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Event Channel Semantics
From: Julian Stecklina <der_julian@xxxxxx>
Date: Thu, 09 Nov 2006 12:03:07 +0100
Delivery-date: Thu, 09 Nov 2006 03:03:39 -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
User-agent: Thunderbird 1.5.0.5 (X11/20060731)
Hello,

I am developing some userspace tools on Xen/Linux and have problems
regarding the semantics of /dev/linux/evtchn. The situation is as follows:

Suppose client A allocates an unbound port.
Client B connects to this via bind_interdomain.
Client A reads on /dev/linux/evtchn to see whether it has been notified.

If client B now notifies client A, the latter gets the correct port from
the call to read(). But all subsequent notifications get lost, and
client A just sits there blocking on read().

Is this intended? If not, where is the problem?

Regards,
Julian Stecklina


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

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