From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Taeung Song <treeze.taeung@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH 1/3] perf ftrace: Remove needless code setting default tracer
Date: Thu, 26 Jan 2017 15:54:58 -0300 [thread overview]
Message-ID: <20170126185458.GT10340@kernel.org> (raw)
In-Reply-To: <1485423339-22780-1-git-send-email-treeze.taeung@gmail.com>
Em Thu, Jan 26, 2017 at 06:35:37PM +0900, Taeung Song escreveu:
> Lately commit a349764 made 'function_graph' be the default tracer.
> So ftrace.tracer variable can't be NULL but the other code setting default
> tracer remained. For this reason, remove it as below.
> And use existing DEFAULT_TRACER instead of "function_graph".
Rewrote a bit the commit log, applied,
- Arnaldo
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
> ---
> tools/perf/builtin-ftrace.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/tools/perf/builtin-ftrace.c b/tools/perf/builtin-ftrace.c
> index d05658d..414444d 100644
> --- a/tools/perf/builtin-ftrace.c
> +++ b/tools/perf/builtin-ftrace.c
> @@ -202,7 +202,7 @@ int cmd_ftrace(int argc, const char **argv, const char *prefix __maybe_unused)
> {
> int ret;
> struct perf_ftrace ftrace = {
> - .tracer = "function_graph",
> + .tracer = DEFAULT_TRACER,
> .target = { .uid = UINT_MAX, },
> };
> const char * const ftrace_usage[] = {
> @@ -231,9 +231,6 @@ int cmd_ftrace(int argc, const char **argv, const char *prefix __maybe_unused)
> if (ret < 0)
> goto out_delete_evlist;
>
> - if (ftrace.tracer == NULL)
> - ftrace.tracer = DEFAULT_TRACER;
> -
> ret = __cmd_ftrace(&ftrace, argc, argv);
>
> out_delete_evlist:
> --
> 2.7.4
next prev parent reply other threads:[~2017-01-26 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 9:35 [PATCH 1/3] perf ftrace: Remove needless code setting default tracer Taeung Song
2017-01-26 9:35 ` [PATCH 2/3] perf ftrace: Add ftrace.tracer config option Taeung Song
2017-01-26 18:58 ` Arnaldo Carvalho de Melo
2017-01-27 2:57 ` Taeung Song
2017-01-27 3:52 ` Taeung Song
2017-01-26 9:35 ` [PATCH 3/3] perf ftrace: Handle NULL at write_tracing_file() Taeung Song
2017-01-26 18:54 ` Arnaldo Carvalho de Melo [this message]
2017-02-01 14:37 ` [tip:perf/core] perf ftrace: Remove needless code setting default tracer tip-bot for Taeung Song
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=20170126185458.GT10340@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=treeze.taeung@gmail.com \
--cc=wangnan0@huawei.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 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.