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

[Xen-devel] mini-os: a event channel experiment

  • To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Y. D." <duyuyang@xxxxxxxxx>
  • Date: Wed, 29 Oct 2008 09:47:34 +0800
  • Delivery-date: Tue, 28 Oct 2008 18:47:59 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:x-mailer:mime-version:content-type; b=VjLLg3vZNqttuvMMrpKBaRoPyewZYvECjHh4I3b84MW6fuSCOy9QfyPtNWIkhxkpPX +pCVF3BPJpPJTFUQY9HIS90SEzT/XHA0aiqMPmRS9AP3DR4WPMW1Lpdz79P/w6B3l+K5 4c6Ve2opY8BqzQ3DwDdPoi6egqsfyjl/iRnko=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi all,
In a mini-os domain A, I start a thread allocating an event channel:
err = evtchn_alloc_unbound(remote_domid, experiment_handler, NULL, &port);
and registered a handler. The err value is 0. The thread normally exits.
While in another mini-os domain B, I start a thread binding that event channel:
err = evtchn_bind_interdomain(remote_domid, remote_port, experiment_handler2, NULL, &port);
and send a event:
err = HYPERVISOR_event_channel_op(EVTCHNOP_send, &event);  Both err is 0. The thread normally exits.
but in the domain A, the event handler is not called.
What is wrong with it?

Y. D.
Xen-devel mailing list



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