From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Cc: "linux-trace-devel@vger.kernel.org" <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH 4/5] fix "trace-cmd reset" command to restore the default value of set_event_pid
Date: Tue, 5 Mar 2019 14:03:58 -0500 [thread overview]
Message-ID: <20190305140358.01b1e0e6@gandalf.local.home> (raw)
In-Reply-To: <20181213142125.12149-5-tstoyanov@vmware.com>
I took the first 3 patches, but fixed the subject to say:
trace-cmd: Fix ....
As all commits should have a "system:" format and the description part
start with a capital letter (note, this is the requirement for the
Linux kernel as well).
On Thu, 13 Dec 2018 14:21:43 +0000
Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:
> The "trace-cmd reset" command should restore ftrace to its default state.
> This patch sets "tracing/set_event_pid" to an empty string,
> when the "trace-cmd reset" command is executed.
>
> Signed-off-by: Tzvetomir Stoyanov <tstoyanov@vmware.com>
> ---
> tracecmd/trace-record.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/tracecmd/trace-record.c b/tracecmd/trace-record.c
> index 38d9871..f77e49a 100644
> --- a/tracecmd/trace-record.c
> +++ b/tracecmd/trace-record.c
> @@ -3761,6 +3761,15 @@ static void reset_clock(void)
> write_instance_file(instance, "trace_clock", "local", "clock");
> }
>
> +static void reset_event_pid(void)
> +{
> + struct buffer_instance *instance;
> +
> + for_all_instances(instance)
> + write_instance_file(instance, "set_event_pid", "", "event_pid");
> +}
Hmm, we should utilize "add_event_pid()" here instead, and simply pass
in an empty line.
Before doing that, make a clean up patch that makes add_event_pid()
utilize write_instance_file() instead of open coding it.
Thanks Tzvetomir!
-- Steve
> +
> +
> static void clear_triggers(void)
> {
> struct buffer_instance *instance;
> @@ -4464,6 +4473,7 @@ void trace_reset(int argc, char **argv)
> clear_triggers();
> /* set clock to "local" */
> reset_clock();
> + reset_event_pid();
> tracecmd_remove_instances();
> clear_func_filters();
> /* restore tracing_on to 1 */
next prev parent reply other threads:[~2019-03-05 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 14:21 [PATCH 0/5] trace-cmd reset fixes Tzvetomir Stoyanov
2018-12-13 14:21 ` [PATCH 1/5] fix "trace-cmd reset" command to restore "tracng_on" Tzvetomir Stoyanov
2018-12-13 14:21 ` [PATCH 2/5] fix "trace-cmd reset -a -d" segfault Tzvetomir Stoyanov
2018-12-13 14:21 ` [PATCH 3/5] fix "trace-cmd reset" command to restore default clock Tzvetomir Stoyanov
2018-12-13 14:21 ` [PATCH 4/5] fix "trace-cmd reset" command to restore the default value of set_event_pid Tzvetomir Stoyanov
2019-03-05 19:03 ` Steven Rostedt [this message]
2018-12-13 14:21 ` [PATCH 5/5] fix "trace-cmd reset" command to restore the default value of tracing_max_latency Tzvetomir Stoyanov
2019-03-05 19:06 ` Steven Rostedt
2019-03-05 13:24 ` [PATCH 0/5] trace-cmd reset fixes Slavomir Kaslev
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=20190305140358.01b1e0e6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tstoyanov@vmware.com \
/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).