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

Re: [Xen-devel] Event channel problems

  • To: Kieran Mansley <kmansley@xxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Tue, 13 Mar 2007 17:19:18 +0000
  • Delivery-date: Tue, 13 Mar 2007 10:18:38 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acdlk7tH+cjaoNGGEduMWwAX8io7RQ==
  • Thread-topic: [Xen-devel] Event channel problems

On 13/3/07 17:07, "Kieran Mansley" <kmansley@xxxxxxxxxxxxxx> wrote:

> However, when the backend then calls:
>         notify_remote_via_evtchn(channel);
> Nothing happens at the frontend.  I was expecting the irq_from_backend()
> function to be called.  There are no errors from any of the above code,
> and the returned values for channels and irqs look very sensible.  Any
> suggestions what I'm doing wrong?

Is channel here the id you got from the frontend? That's not the right thing
to use. Given your backend example code you should
notify_remote_via_irq(channel_irq) (i.e., use the irq number you got back
from bind_interdomain_evtchn_to_irqhandler).

 -- Keir

Xen-devel mailing list



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