From: Vincent Bernardoff <vb@luminar.eu.org>
To: xen-devel@lists.xen.org
Subject: Re: libxc/evtchn: Missed events when using several handles.
Date: Tue, 06 Aug 2013 11:48:27 +0100 [thread overview]
Message-ID: <5200D47B.6070101@luminar.eu.org> (raw)
In-Reply-To: <1375784967.10660.242.camel@kazak.uk.xensource.com>
On 06/08/2013 11:29, Ian Campbell wrote:
> On Tue, 2013-08-06 at 11:15 +0100, Vincent Bernardoff wrote:
>> >Using the attached test programs, the select fails when using h2, and
>> >works with using h1 (line 41).
> What do yo mean by "fails", does it return an error or does it just
> block waiting for an event which never happens?
It does block waiting for an event which never happens.
>> >It seems that using several evtchn handles does not work correctly. What
>> >is the expected behaviour when using multiple event channel handles ?
> You only appear to bind an evtchn to h1, so I would expect that you
> would only see evtchns on h1 and selecting on h2 will just block waiting
> for something to happen,
It seems to be the case.
or maybe h2 will return an error because there
> are no evtchns to wait on.
No, this doesn't happen.
If you bind a different evtchn to h2 then you
> should be able to wait on both h1 and h2.
I thought that an handle was an interface to the eventchn, and that
binding events was completely independant of handles, that is, all
handles receive all events. I was obviously wrong, but it was not clear
to guess.
Thanks,
Vincent.
next prev parent reply other threads:[~2013-08-06 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 10:15 libxc/evtchn: Missed events when using several handles Vincent Bernardoff
2013-08-06 10:29 ` Ian Campbell
2013-08-06 10:48 ` Vincent Bernardoff [this message]
2013-08-06 11:03 ` Ian Campbell
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=5200D47B.6070101@luminar.eu.org \
--to=vb@luminar.eu.org \
--cc=xen-devel@lists.xen.org \
/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.