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

Re: [Xen-devel] xenbus_transaction_end() and EAGAIN

  • To: John Levon <levon@xxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Wed, 04 Oct 2006 08:48:52 +0100
  • Delivery-date: Wed, 04 Oct 2006 00:59:35 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbniYjmx47dYVN8EduVNgANk04WTA==
  • Thread-topic: [Xen-devel] xenbus_transaction_end() and EAGAIN

On 4/10/06 3:13 am, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

> The first is the watch asking us to suspend. Then we get an EAGAIN and
> loop around to try again, but this time the node is rewritten to be "",
> as we requested via xenbus_write(). As far as I can see it shouldn't be
> possible for our xenbus_write("") to have succeeded as part of the
> failed transaction. Is it possible the EAGAIN is coming from the higher
> levels somehow, rather than do_transaction_end() ?

No, the writes should be discarded of course. If xenstored ever returns
EAGAIN it should mean that the transaction was discarded and not committed
in part or whole. Could EAGAIN be coming from the xenbus layers in your
guest OS?

 -- Keir

Xen-devel mailing list



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