From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>,
sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, tim@xen.org, julien.grall@arm.com,
jbeulich@suse.com
Subject: [PATCH 3/3] docs: document CONTROL command of xenstore protocol
Date: Mon, 8 May 2017 09:00:49 +0200 [thread overview]
Message-ID: <20170508070049.29553-4-jgross@suse.com> (raw)
In-Reply-To: <20170508070049.29553-1-jgross@suse.com>
The CONTROL command (former DEBUG command) isn't specified in the
xenstore protocol doc. Add it.
Signed-off-by: Juergen Gross <jgross@suse.com>
---
docs/misc/xenstore.txt | 29 +++++++++++++++++++++++------
1 file changed, 23 insertions(+), 6 deletions(-)
diff --git a/docs/misc/xenstore.txt b/docs/misc/xenstore.txt
index fd38d781e2..074650f144 100644
--- a/docs/misc/xenstore.txt
+++ b/docs/misc/xenstore.txt
@@ -319,12 +319,29 @@ SET_TARGET <domid>|<tdomid>|
---------- Miscellaneous ----------
-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.
+ Current commands are:
+ check
+ checks xenstored innards
+ log|on
+ turn xenstore logging on
+ log|off
+ turn xenstore logging off
+ logfile|<file-name>
+ log to specified file
+ memreport|[<file-name>]
+ print memory statistics to logfile (no <file-name>
+ specified) or to specific file
+ print|<string>
+ print <string> to syslog (xenstore runs as daemon) or
+ to console (xenstore runs as stubdom)
+ help <supported-commands>
+ return list of supported commands for CONTROL
+DEBUG
+ Deprecated, now named CONTROL
--
2.12.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-08 7:00 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 ` Juergen Gross [this message]
2017-05-08 10:13 ` [PATCH 3/3] docs: document CONTROL command of xenstore protocol Ian Jackson
2017-05-08 10:22 ` Juergen Gross
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=20170508070049.29553-4-jgross@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).