public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Howard Cochran <hcochran@kernelspring.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Howard Cochran <hcochran@kernelspring.com>,
	linux-kernel@vger.kernel.org,
	Howard Cochran <cochran@lexmark.com>
Subject: [PATCH v3 0/5] trace-cmd: Improve multi-instance support
Date: Wed, 22 Apr 2015 00:55:09 -0400	[thread overview]
Message-ID: <cover.1429677461.git.hcochran@kernelspring.com> (raw)

NOTE: The previous two versions of this patch set were distributed off-list.

v3 changes:
    * Improved clarification of options in documentation of
      trace-cmd reset and added examples.

v2 changes:
    * Rebased this patch series on Steve's simplification of
      first_instance logic.

Improve the completeness and consistency of support for multiple
buffer instances in the extract, snapshot, stat, start, stop,
reset, and restart sub-commands.

For the commands that lacked it, added support for -B and -t options,
consistent with the existing behavior of stop, reset, and restart.
That is, including a -B instance-name option will cause these commands to
exclude the top buffer instance unless -t is also provided.

Exception: trace-cmd start retains its existing behavior regarding the
top instance, consistent with trace-cmd record.

For all of these sub-commands except start, add a new -a option, which
causes it to operate on all existing instances.  As with -B, -a will
exclude the top instance unless -t is also given.

Updated documentation accordingly.


Howard Cochran (5):
  trace-cmd extract: Add -B and -t for multiple instances
  trace-cmd extract: Add -a option for all instances
  trace-cmd stop, reset, restart: Add -a for all instances
  trace-cmd snapshot: Fully support multiple instances
  trace-cmd stat: Support -a for all buffers. Update docs.

 Documentation/trace-cmd-extract.1.txt  |  16 ++++
 Documentation/trace-cmd-reset.1.txt    |  57 ++++++++++--
 Documentation/trace-cmd-snapshot.1.txt |  16 +++-
 Documentation/trace-cmd-stat.1.txt     |  19 ++++
 Documentation/trace-cmd-stop.1.txt     |  13 ++-
 trace-cmd.c                            |   2 +-
 trace-local.h                          |   6 +-
 trace-record.c                         | 160 ++++++++++++++++++++++++++++-----
 trace-snapshot.c                       |  90 ++++++++++---------
 trace-stat.c                           |  15 +++-
 trace-usage.c                          |  42 ++++++---
 11 files changed, 341 insertions(+), 95 deletions(-)

-- 
1.9.1


             reply	other threads:[~2015-04-22  4:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22  4:55 Howard Cochran [this message]
2015-04-22  4:55 ` [PATCH v3 1/5] trace-cmd extract: Add -B and -t for multiple instances Howard Cochran
2015-04-22  4:55 ` [PATCH v3 2/5] trace-cmd extract: Add -a option for all instances Howard Cochran
2015-04-22  4:55 ` [PATCH v3 3/5] trace-cmd stop, reset, restart: Add -a " Howard Cochran
2015-04-22  4:55 ` [PATCH v3 4/5] trace-cmd snapshot: Fully support multiple instances Howard Cochran
2015-04-22  4:55 ` [PATCH v3 5/5] trace-cmd stat: Support -a for all buffers. Update docs Howard Cochran

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=cover.1429677461.git.hcochran@kernelspring.com \
    --to=hcochran@kernelspring.com \
    --cc=cochran@lexmark.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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