[PATCH v3 0/5] trace-cmd: Improve multi-instance support

From: Howard Cochran
Date: Wed Apr 22 2015 - 00:56:41 EST


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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/