From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefan Bader <stefan.bader@canonical.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: xenbus and the message of doom
Date: Mon, 2 Jan 2012 18:16:31 +0100 [thread overview]
Message-ID: <20120102171631.GA13603@aepfle.de> (raw)
In-Reply-To: <1324412394.8252.163.camel@dagon.hellion.org.uk>
On Tue, Dec 20, Ian Campbell wrote:
> On Tue, 2011-12-20 at 17:29 +0000, Ian Jackson wrote:
> > Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] xenbus and the message of doom"):
> > > Sorry Olaf, have to revert that commit.
> >
> > I agree. When we introduced it we weren't aware that most existing
> > implementations of xenstored simply ignore unknown commands rather
> > than replying with an error. If we had known this we would not have
> > approved Olaf's patch.
> >
> > That they ignore unknown commands is of course a bug but expecting
> > everyone to update is no good. Really the best approach would be some
> > kind of discovery mechanism.
> >
> > Maybe we should have a special path @xenstore/fail_unknown_commands
> > which you could read, or something. But this time we should try it
> > against old implementations.
>
> I was sure I'd seen some precedent (and therefore an existing path) for
> this sort of thing at some point but I can't for the life of me find it.
If you could come up with a patch to present xenstored (or other
dom0/toolstack) features, that would be great.
Olaf
next prev parent reply other threads:[~2012-01-02 17:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 19:20 xenbus and the message of doom Stefan Bader
2011-12-15 19:39 ` Konrad Rzeszutek Wilk
2011-12-15 19:45 ` Stefan Bader
2011-12-16 11:33 ` Olaf Hering
2011-12-16 15:25 ` Konrad Rzeszutek Wilk
2012-01-02 9:32 ` Stefan Bader
2011-12-20 10:11 ` Ian Campbell
2011-12-20 13:15 ` Olaf Hering
2011-12-20 14:16 ` Konrad Rzeszutek Wilk
2011-12-20 17:29 ` Ian Jackson
2011-12-20 20:19 ` Ian Campbell
2012-01-02 17:16 ` Olaf Hering [this message]
2012-01-03 11:01 ` Ian Campbell
2012-01-04 15:57 ` Olaf Hering
2012-01-04 16:22 ` Ian Campbell
2012-01-04 16:27 ` Olaf Hering
2012-01-05 9:26 ` Ian Campbell
2012-01-05 18:43 ` Olaf Hering
2012-01-02 9:29 ` Stefan Bader
2011-12-15 20:53 ` Ian Campbell
2011-12-16 9:18 ` Stefan Bader
2011-12-16 9:31 ` Ian Campbell
2011-12-16 17:01 ` Olaf Hering
2011-12-16 21:26 ` Alessandro Salvatori
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=20120102171631.GA13603@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=stefan.bader@canonical.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 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.