xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: race in xenstore?
Date: Tue, 27 Apr 2010 10:38:42 +0200	[thread overview]
Message-ID: <4BD6A292.9000408@ts.fujitsu.com> (raw)

Hi,

I observe a strange behaviour with our BS2000 guest reading xenstore:

When the domU is started, we are reading some values from xenstore, which are
written by a backend driver on dom0. One special entry is used for signalling
validity of the other entries. The domU tries to read it until the entry is
existing. The value of this entry is always a numerical value greater 0.

In rare cases I see the following behaviour (extracted from xenstore.log):

- the domU tries to read the entry, xenstored seems not to know it:
    IN 0x61b9c0 20100423 22:25:42 READ (bs2/vmid )
    OUT 0x61b9c0 20100423 22:25:42 ERROR (ENOENT )
- on domU side, I don't see the ENOENT, but read the string "OK"!
- a little bit later (same second) the entry is written by dom0:
    IN 0x625c50 20100423 22:25:42 WRITE (/local/domain/169/bs2/vmid 2)
    OUT 0x625c50 20100423 22:25:42 WRITE (OK )

Xen version is 3.3.1

I'm not familiar with the xenstored internals, perhaps someone has an idea
what is happening here?


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

             reply	other threads:[~2010-04-27  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27  8:38 Juergen Gross [this message]
2010-04-28  0:46 ` race in xenstore? Keir Fraser

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=4BD6A292.9000408@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).