| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] [RESEND] evtchn sanity check |
| From: | "King, Steven R" <steven.r.king@xxxxxxxxx> |
| Date: | 2005年10月18日 16:04:20 -0700 |
| Delivery-date: | 2005年10月18日 23:04:08 +0000 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| 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> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
| 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. Thanks, -steve _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH][RESEND] Make xend set the console limit , Ewan Mellor |
|---|---|
| Next by Date: | RE: [Xen-devel] dom0 oom-killer: gfp_mask=0x1d , Ted Kaczmarek |
| Previous by Thread: | [Xen-devel] [PATCH][RESEND] Make xend set the console limit , Dan Smith |
| Next by Thread: | [Xen-devel] Staus of split lock in pfn_inf on x86_64 , Nakajima, Jun |
| Indexes: | [Date] [Thread] [Top] [All Lists] |