From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v4 0/4] Extend coverage of "trace-cmd reset" command
Date: Tue, 25 Feb 2020 20:07:29 +0200 [thread overview]
Message-ID: <20200225180733.89344-1-tz.stoyanov@gmail.com> (raw)
The "trace-cmd reset" command is supposed to set the ftrace state to default.
However, some ftrace configurations are not reseted: synthetic events and
error_log file. The command is extended to clean these.
Two new tracefs APIs were also implemented, to check if given ftrace
file / directory exists:
bool tracefs_file_exist(struct tracefs_instance *instance, char *name);
bool tracefs_dir_exist(struct tracefs_instance *instance, char *name);
[
v2 changes:
- Removed these patches from the "SQL-like syntax for ftrace histograms
configuration" patch set, as they are not directly related to it.
v3 changes:
- Remove the warning in case there are no configured synthetic events.
v4 chanegs:
- Implemented new tracefs APIs to check if given ftrace file /
directory exists. Use the new APIs to check if synthetic_events and
error_log files exist, before accessing them.
]
Tzvetomir Stoyanov (VMware) (4):
trace-cmd: Add new tracefs APIs for checking if a ftrace file /
directory exists
trace-cmd: Unit tests for new libtracefs APIs
trace-cmd: Clear synthetic events on reset subcommand
trace-cmd: Clear error log on reset subcommand
include/tracefs/tracefs.h | 3 ++
lib/tracefs/tracefs-instance.c | 49 ++++++++++++++++++++++++++-
tracecmd/trace-record.c | 61 ++++++++++++++++++++++++++++++++++
utest/tracefs-utest.c | 16 +++++++++
4 files changed, 128 insertions(+), 1 deletion(-)
--
2.24.1
next reply other threads:[~2020-02-25 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 18:07 Tzvetomir Stoyanov (VMware) [this message]
2020-02-25 18:07 ` [PATCH v4 1/4] trace-cmd: Add new tracefs APIs for checking if a ftrace file / directory exists Tzvetomir Stoyanov (VMware)
2020-04-09 18:22 ` Steven Rostedt
2020-04-13 6:52 ` Tzvetomir Stoyanov
2020-02-25 18:07 ` [PATCH v4 2/4] trace-cmd: Unit tests for new libtracefs APIs Tzvetomir Stoyanov (VMware)
2020-02-25 18:07 ` [PATCH v4 3/4] trace-cmd: Clear synthetic events on reset subcommand Tzvetomir Stoyanov (VMware)
2020-02-25 18:07 ` [PATCH v4 4/4] trace-cmd: Clear error log " Tzvetomir Stoyanov (VMware)
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=20200225180733.89344-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 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).