All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>,
	wei.liu2@citrix.com, ian.jackson@eu.citrix.com
Subject: [PATCH v2 0/5] xenstore: enhance runtime debug capabilities
Date: Tue, 21 Feb 2017 16:07:32 +0100	[thread overview]
Message-ID: <20170221150737.30589-1-jgross@suse.com> (raw)

Today xenstored supports logging only via a command line parameter.
This means that logging is either all the time off (default) or on.
To switch logging on the Xen host has to be rebooted as xenstored
isn't restartable.

This patch series changes this by using the XS_DEBUG wire command of
Xenstore to control various debug functions:

- switch logging on/off
- specify logfile to use
- write memory usage to file

This will enable the host administrator to control above functionality
without the need of specifying any additional command line parameters
of xenstored or to restart the host in case of debug information
needed.

Changes in V2:
- added new patch 1 (rename of XS_DEBUG to XS_CONTROL)

Juergen Gross (5):
  xenstore: rename XS_DEBUG wire command
  xenstore: enhance control command support
  xenstore: add support for changing log functionality dynamically
  xenstore: make memory report available via XS_CONTROL
  xenstore: remove memory report command line support

 tools/xenstore/Makefile            |   4 +-
 tools/xenstore/include/xenstore.h  |   2 +-
 tools/xenstore/xenstore_control.c  |  65 +++++++++----
 tools/xenstore/xenstored_control.c | 194 +++++++++++++++++++++++++++++++++++++
 tools/xenstore/xenstored_control.h |  19 ++++
 tools/xenstore/xenstored_core.c    |  81 ++++------------
 tools/xenstore/xenstored_core.h    |   6 +-
 tools/xenstore/xs.c                |   7 +-
 xen/include/public/io/xs_wire.h    |   3 +-
 9 files changed, 290 insertions(+), 91 deletions(-)
 create mode 100644 tools/xenstore/xenstored_control.c
 create mode 100644 tools/xenstore/xenstored_control.h

-- 
2.10.2


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2017-02-21 15:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 15:07 Juergen Gross [this message]
2017-02-21 15:07 ` [PATCH v2 1/5] xenstore: rename XS_DEBUG wire command Juergen Gross
2017-02-22 12:36   ` Wei Liu
2017-02-22 12:40     ` Juergen Gross
2017-02-22 12:43       ` Wei Liu
2017-02-22 12:44         ` Juergen Gross
2017-02-21 15:07 ` [PATCH v2 2/5] xenstore: enhance control command support Juergen Gross
2017-02-22 12:36   ` Wei Liu
2017-02-22 12:41     ` Juergen Gross
2017-02-21 15:07 ` [PATCH v2 3/5] xenstore: add support for changing log functionality dynamically Juergen Gross
2017-02-22 12:36   ` Wei Liu
2017-02-22 12:42     ` Juergen Gross
2017-02-21 15:07 ` [PATCH v2 4/5] xenstore: make memory report available via XS_CONTROL Juergen Gross
2017-02-22 12:36   ` Wei Liu
2017-02-22 12:43     ` Juergen Gross
2017-02-22 12:47       ` Wei Liu
2017-02-22 12:48         ` Juergen Gross
2017-02-21 15:07 ` [PATCH v2 5/5] xenstore: remove memory report command line support 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=20170221150737.30589-1-jgross@suse.com \
    --to=jgross@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --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 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.