From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julian Stecklina <der_julian@web.de>
Subject: Event Channel Semantics
Date: Thu, 09 Nov 2006 12:03:07 +0100
Message-ID: <eiv1tb$8t5$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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