From: Juergen Gross <jgross@suse.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
tim@xen.org, julien.grall@arm.com, jbeulich@suse.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 3/3] docs: document CONTROL command of xenstore protocol
Date: Mon, 8 May 2017 12:22:33 +0200 [thread overview]
Message-ID: <fe02ed53-76b2-da5a-dd6f-b27e6cd0bbbe@suse.com> (raw)
In-Reply-To: <22800.17597.555059.289271@mariner.uk.xensource.com>
On 08/05/17 12:13, Ian Jackson wrote:
> Juergen Gross writes ("[PATCH 3/3] docs: document CONTROL command of xenstore protocol"):
>> The CONTROL command (former DEBUG command) isn't specified in the
>> xenstore protocol doc. Add it.
> ...
>> -DEBUG print|<string>|?? sends <string> to debug log
>> -DEBUG print|<thing-with-no-nul> EINVAL
>> -DEBUG check|?? checks xenstored innards
>> -DEBUG <anything-else|> no-op (future extension)
>> +CONTROL <command>|[<parameters>|]
>> + Send a control command <command> with optional parameters
>> + (<parameters>) to Xenstore daemon. <command> support is
>> + implementation specific and might change in future.
>>
>> - These requests should not generally be used and may be
>> - withdrawn in the future.
>
> I should retain a stronger imprecation. How about:
>
> The set of commands and their semantics is implementation
> specific and is likely to change from one Xen version to the
> next. Out-of-tree users will encounter compatibility issues.
I'm fine with this.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-08 10:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 7:00 [PATCH 0/3] docs: add some missing xenstore documentation Juergen Gross
2017-05-08 7:00 ` [PATCH 1/3] docs: specify endianess of xenstore protocol header Juergen Gross
2017-05-08 7:00 ` [PATCH 2/3] docs: add DIRECTORY_PART specification do xenstore protocol doc Juergen Gross
2017-05-08 10:09 ` Ian Jackson
2017-05-08 10:31 ` Juergen Gross
2017-05-08 11:53 ` Ian Jackson
2017-05-08 12:33 ` Juergen Gross
2017-05-08 7:00 ` [PATCH 3/3] docs: document CONTROL command of xenstore protocol Juergen Gross
2017-05-08 10:13 ` Ian Jackson
2017-05-08 10:22 ` Juergen Gross [this message]
2017-05-08 10:39 ` [PATCH 0/3] docs: add some missing xenstore documentation Julien Grall
-- strict thread matches above, loose matches on Subject: below --
2017-05-08 6:58 Juergen Gross
2017-05-08 6:58 ` [PATCH 3/3] docs: document CONTROL command of xenstore protocol Juergen Gross
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=fe02ed53-76b2-da5a-dd6f-b27e6cd0bbbe@suse.com \
--to=jgross@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).