I don't see anything wrong with your code... are you sure the minios is 
behaving itself and sending the events? Have you tried putting printks in 
there to see if it's definitely successfully operating?
Are you sure the value of "port" you're binding in dom0 is correct? If 
necessary, you could try adding tracing code to the Linux evtchn driver.
I can't quite see what's going wrong from the code you posted, sorry not to be 
more helpful.
Cheers,
Mark
On Friday 12 January 2007 18:33, Julian Stecklina wrote:
> Hello,
>
> in an application I develop, event channel semantics seem a bit odd to
> me. Consider the following scenario: A Mini-OS binds an unbound port for
> domain 0 and issues a notification every second:
>
> evtchn_alloc_unbound(0, msg_handler, NULL,
> &port);
>
> printk("%u %u %u\n", domid, port);
>
> while (1) {
> sleep(1000);
> notify_remote_via_evtchn(port);
> }
>
> A Linux program running on Domain 0 calls bind_interdomain using domid
> and port to obtain local_port and watches for pending notifications:
>
> evtchn_port_t local_port = xc_evtchn_bind_interdomain(ev, domid, port);
>
> while (1) {
> evtchn_port_t port;
>
> port = xc_evtchn_pending(ev);
> printf("%u\n", port);
> xc_evtchn_unmask(ev, port);
> }
>
> Now what I do not understand is, why the Linux program sees exactly one
> notification and then indefinitely blocks. Any help on what I may be
> doing wrong is greatly appreciated. This is with xen-3.0.4-testing.
>
> Regards,
> Julian
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel 
-- 
Dave: Just a question. What use is a unicyle with no seat? And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel