WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xenbus watch firing over and over

To: Jacob Gorm Hansen <jacobg@xxxxxxx>
Subject: Re: [Xen-devel] Xenbus watch firing over and over
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Wed, 3 Jan 2007 18:25:39 +0000
Cc: xen-devel <Xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 03 Jan 2007 10:25:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1167848163.2591.5.camel@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1167848163.2591.5.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Wed, Jan 03, 2007 at 07:16:03PM +0100, Jacob Gorm Hansen wrote:

> hi,
> I am trying to add xenbus watch support to mini-os, but am getting into
> a endless loop of watches firing over and over. Below is an excerpt from
> the xenstore tracefile:
> 
> IN  0x805acc8 20070103 19:32:18 WATCH
> (/local/domain/0/backend/vif/26/0/state 00043818 )
> CREATE watch 0x805a8b8
> OUT 0x805acc8 20070103 19:32:18 WATCH (OK )
> OUT 0x805acc8 20070103 19:32:18 WATCH_EVENT
> (/local/domain/0/backend/vif/26/0/state 00043818 )
> IN  0x805acc8 20070103 19:32:18 UNWATCH
> (/local/domain/0/backend/vif/26/0/state 00043818 )
> DESTROY watch 0x805a8b8
> OUT 0x805acc8 20070103 19:32:18 UNWATCH (OK )
> IN  0x805acc8 20070103 19:32:18 READ
> (/local/domain/0/backend/vif/26/0/state )
> OUT 0x805acc8 20070103 19:32:18 READ (5)
> IN  0x805acc8 20070103 19:32:18 WATCH
> (/local/domain/0/backend/vif/26/0/state 00043818 )
> CREATE watch 0x806af60
> OUT 0x805acc8 20070103 19:32:18 WATCH (OK )
> OUT 0x805acc8 20070103 19:32:18 WATCH_EVENT
> (/local/domain/0/backend/vif/26/0/state 00043818 )
> IN  0x805acc8 20070103 19:32:18 UNWATCH
> (/local/domain/0/backend/vif/26/0/state 00043818 )
> DESTROY watch 0x806af60
> OUT 0x805acc8 20070103 19:32:18 UNWATCH (OK )
> IN  0x805acc8 20070103 19:32:18 READ
> (/local/domain/0/backend/vif/26/0/state )
> OUT 0x805acc8 20070103 19:32:18 READ (5)
> IN  0x805acc8 20070103 19:32:18 WATCH
> (/local/domain/0/backend/vif/26/0/state 00043818 )
> 
> ...
> 
> The same watch seems to be firing again and again, even though noone
> appears to be writing it. Should I some ack the watch, or is this a bug
> in xenstored?

As far as xenstored is concerned, someone is explicitly deleting and
reregistering that watch -- I don't think this is a bug in xenstored.  You
should expect to receive a watch event as soon as a watch is registered -- it
looks to me like someone is receiving that event, then unwatching the node,
reading its value, and reregistering the watch.

Ewan.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>