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

Re: [Xen-devel] event_lock not initialized in the idle domain (permitted actions in a tasklet?)


  • To: "Byrne, John (HP Labs)" <john.l.byrne@xxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Tue, 27 Apr 2010 06:48:48 +0100
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 26 Apr 2010 22:50:15 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcriXnhomNarVb6UQu+V77DxbzJ2aAAAtYXcAAAFtnAAFMrLrQAjuYDwABPekEMAc9fMIAAav54m
  • Thread-topic: [Xen-devel] event_lock not initialized in the idle domain (permitted actions in a tasklet?)

On 27/04/2010 00:01, "Byrne, John (HP Labs)" <john.l.byrne@xxxxxx> wrote:

>> I don't know what dom0 does while the page is paged in? Probably just
>> throws an error code and carries on? In which case thinking about
>> [prepare_]wait_on_xen_event_channel() further would not be necessary,
>> as a dom0 code path can just notify on teh channel and carry on its
>> way.
>> 
> 
> That is the way it is supposed to work, but there seems to be a bit of a
> disconnect between grant-table code and the driver mods to handle the errors.
> The driver mods expect a new error code GNTST_eagain, but the grant_table code
> returns ENOENT in a couple of places. There were also a couple of
> "GNTxxx_can_fail" flags added to grant-table interface, but they are unused.
> So things don't look quite finished.

Yeah, I think that is pretty much the situation.

 -- Keir



_______________________________________________
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®.