All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/2] Enhancements to trace-cmd clear
Date: Fri, 17 Jul 2020 11:03:24 +0300	[thread overview]
Message-ID: <20200717080326.82151-1-tz.stoyanov@gmail.com> (raw)

Added new options to trace-cmd clear, alowwing it to be ftrace instance
aware.
Implemented new tracefs API for iterating over the configured ftrace
instances.

Tzvetomir Stoyanov (VMware) (2):
  trace-cmd: Add new tracefs API tracefs_instances_walk()
  trace-cmd: Enhance "trace-cmd clear" to be instance aware

 Documentation/trace-cmd-clear.1.txt |  13 ++-
 include/tracefs/tracefs.h           |   1 +
 lib/tracefs/include/tracefs-local.h |   1 +
 lib/tracefs/tracefs-events.c        |  14 ++--
 lib/tracefs/tracefs-instance.c      |  52 ++++++++++++
 tracecmd/Makefile                   |   1 +
 tracecmd/trace-clear.c              | 124 ++++++++++++++++++++++++++++
 tracecmd/trace-record.c             |  24 ------
 tracecmd/trace-stat.c               |  52 +++---------
 tracecmd/trace-usage.c              |   4 +-
 10 files changed, 214 insertions(+), 72 deletions(-)
 create mode 100644 tracecmd/trace-clear.c

-- 
2.26.2


             reply	other threads:[~2020-07-17  8:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17  8:03 Tzvetomir Stoyanov (VMware) [this message]
2020-07-17  8:03 ` [PATCH 1/2] trace-cmd: Add new tracefs API tracefs_instances_walk() Tzvetomir Stoyanov (VMware)
2020-07-17 13:25   ` Steven Rostedt
2020-07-17  8:03 ` [PATCH 2/2] trace-cmd: Enhance "trace-cmd clear" to be instance aware Tzvetomir Stoyanov (VMware)
2020-07-17 13:31   ` Steven Rostedt
2020-07-17 14:06   ` Steven Rostedt
2020-07-17 14:29     ` Tzvetomir Stoyanov

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=20200717080326.82151-1-tz.stoyanov@gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=linux-trace-devel@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 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.