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

[Xen-devel] XEN event channel (interdomain communication)


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Sankaran Sivathanu <ssankaran@xxxxxxxxx>
  • Date: Sun, 27 Feb 2011 19:02:06 -0500
  • Delivery-date: Sun, 27 Feb 2011 16:03:25 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=lNZN1mxU7qvL4Z8U5XTO8IKYYMv/LEmdtRTHWM+JQ2v/SOXTr8hIRO0mkRZU9SsACA SLc4axESLbDg8Z99vol5QDfOgkm2+8mNsB0STk8OBTrEpvCZHQRKLsS2AUYK3Efex1oU E+uVxIBEg7eDbxq6swQSGhf09cVHisqt+kDNE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi, 

Could someone please briefly explain the differences between these calls in the XEN event channel framework ?  I couldn't find resources that talk about these calls.. 

My goal is simple: send an event from Dom0 to DomU and invoke a handler in DomU when an event is received.   I wish to do this in kernel level.. I am a bit confused on what calls to use and also about how to allocate port numbers.  So it would be really helpful if someone could tell the purpose of these calls.. 

bind_caller_port_to_irq
bind_listening_port_to_irq
bind_listening_port_to_irq
bind_interdomain_evtchn_to_irq


bind_caller_port_to_irqhandler
bind_listening_port_to_irqhandler
bind_listening_port_to_irqhandler
bind_interdomain_evtchn_to_irqhandler


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

 


Rackspace

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