From: Jacob Gorm Hansen <jacobg@diku.dk>
To: xen-devel <Xen-devel@lists.xensource.com>
Subject: Xenbus watch firing over and over
Date: Wed, 03 Jan 2007 19:16:03 +0100 [thread overview]
Message-ID: <1167848163.2591.5.camel@localhost.localdomain> (raw)
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?
This is with Xen 3.0.3.
Regards,
Jacob
next reply other threads:[~2007-01-03 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 18:16 Jacob Gorm Hansen [this message]
2007-01-03 18:25 ` Xenbus watch firing over and over Ewan Mellor
2007-01-04 12:18 ` Jacob Gorm Hansen
2007-01-04 12:28 ` Ewan Mellor
2007-01-05 11:21 ` Grzegorz Milos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1167848163.2591.5.camel@localhost.localdomain \
--to=jacobg@diku.dk \
--cc=Xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.