From: Steven Rostedt <rostedt@goodmis.org>
To: <linux-trace-devel@vger.kernel.org>
Cc: Nicolas Sterchele <nicolas@sterchelen.net>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>
Subject: [PATCH v2 0/3] trace-cmd: Add more ways to view options
Date: Thu, 22 Apr 2021 17:18:00 -0400 [thread overview]
Message-ID: <20210422211803.862397-1-rostedt@goodmis.org> (raw)
From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
When testing the func-norepeats patch series from Yordan, I wanted a way
to see what options were enabled for all tracers without having to
enable a tracer first.
Change trace-cmd list to look at the options in the options directory
instead of the trace_options file, as the trace_options file only shows
the options for the current tracer and global options. The options
directory shows all options since Linux 4.4.
Add -o to stat to display the options, as stat lets you see instances
where as list does not.
Changes since v1:
- Included the --full patch, to remove flags from a die() call.
- Removed extra changes that did not belong to this patch series.
- Rebased on top of the --full patch.
Steven Rostedt (VMware) (3):
trace-cmd list: Add --full to show print fmt of an event
trace-cmd list: Use tracefs to help find events for -e
trace-cmd list: Add ftrace events to listing of events
Documentation/trace-cmd/trace-cmd-list.1.txt | 5 +-
tracecmd/trace-list.c | 179 +++++++++++++++++--
tracecmd/trace-usage.c | 1 +
3 files changed, 168 insertions(+), 17 deletions(-)
--
2.29.2
next reply other threads:[~2021-04-22 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 21:18 Steven Rostedt [this message]
2021-04-22 21:18 ` [PATCH v2 1/3] trace-cmd list: Add --full to show print fmt of an event Steven Rostedt
2021-04-22 21:18 ` [PATCH v2 2/3] trace-cmd list: Use tracefs to help find events for -e Steven Rostedt
2021-04-22 21:18 ` [PATCH v2 3/3] trace-cmd list: Add ftrace events to listing of events Steven Rostedt
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=20210422211803.862397-1-rostedt@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=nicolas@sterchelen.net \
/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).