All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Stecklina <der_julian@web.de>
To: xen-devel@lists.xensource.com
Subject: Event Channel Semantics
Date: Thu, 09 Nov 2006 12:03:07 +0100	[thread overview]
Message-ID: <eiv1tb$8t5$1@sea.gmane.org> (raw)

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

             reply	other threads:[~2006-11-09 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09 11:03 Julian Stecklina [this message]
2006-11-09 15:34 ` Event Channel Semantics Mark Williamson
2006-11-16  1:06   ` Julian Stecklina
2006-11-16  1:08     ` John Levon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='eiv1tb$8t5$1@sea.gmane.org' \
    --to=der_julian@web.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.