From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Keir Fraser <Keir.Fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Yu Zhiguo <yuzg@cn.fujitsu.com>
Subject: Re: why xenstore-* hangs if xenstored is not started
Date: Tue, 22 Jun 2010 09:26:59 +0100 [thread overview]
Message-ID: <4C2073D3.1060101@eu.citrix.com> (raw)
In-Reply-To: <C8462D7A.18296%keir.fraser@eu.citrix.com>
On 22/06/10 09:06, Keir Fraser wrote:
> On 22/06/2010 08:56, "Vincent Hanquez"<Vincent.Hanquez@eu.citrix.com>
> wrote:
>
>> On 22/06/10 08:45, Keir Fraser wrote:
>>> Does the xenstore driver in the dom0 kernel put the process into
>>> uninterruptible sleep? The 2.6.18 kernel simply returns -ENODEV in this case
>>> I think. So perhaps pv_ops has different and inferior behaviour.
>>
>> the behavior was the same in 2.6.18.
>
> Ah, I just see 'if (!is_xenstored_ready()) return -ENODEV' in 2.6.18's
> xenbus_dev.c. I assumed that would have an effect on this case.
hm, maybe it does afterall, and I'm confuse this with a more general
case; the D state would happens if xenstored doesn't want to reply or is
dead. This behavior has been there as long as I can remember.
I'm pretty sure though that a while ago (relatively old XenServer
kernel) starting a xenstore-* without starting xenstored would make it
stuck until xenstored start.
--
Vincent
next prev parent reply other threads:[~2010-06-22 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 7:32 why xenstore-* hangs if xenstored is not started Yu Zhiguo
2010-06-22 7:44 ` Vincent Hanquez
2010-06-22 7:58 ` Yu Zhiguo
2010-06-22 8:27 ` Vincent Hanquez
2010-06-22 8:46 ` Yu Zhiguo
2010-06-22 7:45 ` Keir Fraser
2010-06-22 7:56 ` Vincent Hanquez
2010-06-22 8:06 ` Keir Fraser
2010-06-22 8:26 ` Vincent Hanquez [this message]
2010-06-22 8:12 ` Yu Zhiguo
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=4C2073D3.1060101@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yuzg@cn.fujitsu.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).