This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] event_lock not initialized in the idle domain (permitted

To: "Byrne, John (HP Labs)" <john.l.byrne@xxxxxx>
Subject: Re: [Xen-devel] event_lock not initialized in the idle domain (permitted actions in a tasklet?)
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
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <469F2699A483D44BA6D2B311B1089D3A7B094C2108@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcriXnhomNarVb6UQu+V77DxbzJ2aAAAtYXcAAAFtnAAFMrLrQAjuYDwABPekEMAc9fMIAAav54m
Thread-topic: [Xen-devel] event_lock not initialized in the idle domain (permitted actions in a tasklet?)
User-agent: Microsoft-Entourage/
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