|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Event Channel Semantics
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>
|
- [Xen-devel] Event Channel Semantics,
Julian Stecklina <=
|
|
|
|
|