WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] evtchn sanity check

To: "King, Steven R" <steven.r.king@xxxxxxxxx>
Subject: Re: [Xen-devel] evtchn sanity check
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 19 Oct 2005 07:06:34 +0100
Cc: xen-devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 19 Oct 2005 06:16:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <44BDAFB888F59F408FAE3CC35AB470410235EB93@orsmsx409>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <44BDAFB888F59F408FAE3CC35AB470410235EB93@orsmsx409>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

This is all correct. The only things read/written from/to the device are 16-bit port numbers.

 -- Keir

On 18 Oct 2005, at 22:30, King, Steven R wrote:

Would appreciate a sanity check on my understanding:

When doing a read() from an interdomain event channel file descriptor
(/dev/xen/evtchn), the values read are 16-bit port numbers on which
there is an event.  Is there ever anything else that is read() from the
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.

Thanks for the time,
-steve

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>