[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [RESEND] evtchn sanity check

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "King, Steven R" <steven.r.king@xxxxxxxxx>
  • Date: Tue, 18 Oct 2005 16:04:20 -0700
  • Delivery-date: Tue, 18 Oct 2005 23:04:08 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXUKzAt1qMHpo48TpC+6vZTQE12rw==
  • Thread-topic: [RESEND] evtchn sanity check

Apologies if this comes through twice.
Would appreciate a sanity check on my understanding:

A read() from an interdomain event channel file descriptor
(/dev/xen/evtchn) returns 16-bit port numbers on which there is an
event.  Is there ever anything else that is read() from the interdomain
event channel?

When doing a write() on an interdomain event channel file descriptor,
the data written are 16-bit port values for which events should be
enabled (or generated?).  Is there ever anything else that is write()'n
to an event channel?

After doing a notify() IOCTL on an interdomain event channel, a read()
on the remote file descriptor returns the 16-bit port number that
received the notify.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.