From: Jiri Olsa <jolsa@redhat.com>
To: kan.liang@intel.com
Cc: acme@kernel.org, jolsa@kernel.org, namhyung@kernel.org,
ak@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC V4 1/4] perf,tools: introduce callgraph_set for callgraph option
Date: Fri, 17 Jul 2015 11:23:57 +0200 [thread overview]
Message-ID: <20150717092357.GA1057@krava.redhat.com> (raw)
In-Reply-To: <1437035170-12911-2-git-send-email-kan.liang@intel.com>
On Thu, Jul 16, 2015 at 04:26:07AM -0400, kan.liang@intel.com wrote:
> From: Kan Liang <kan.liang@intel.com>
>
> Introduce callgraph_set to indicate whether the callgraph option was set
> by user.
>
> Signed-off-by: Kan Liang <kan.liang@intel.com>
> ---
> tools/perf/builtin-record.c | 6 ++++--
> tools/perf/perf.h | 1 +
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 283fe96..1d40be9 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -762,12 +762,13 @@ static void callchain_debug(void)
> callchain_param.dump_size);
> }
>
> -int record_parse_callchain_opt(const struct option *opt __maybe_unused,
> +int record_parse_callchain_opt(const struct option *opt,
> const char *arg,
> int unset)
> {
> int ret;
>
> + *(bool *)opt->set = true;
> callchain_param.enabled = !unset;
>
> /* --no-call-graph */
> @@ -784,10 +785,11 @@ int record_parse_callchain_opt(const struct option *opt __maybe_unused,
> return ret;
> }
>
> -int record_callchain_opt(const struct option *opt __maybe_unused,
> +int record_callchain_opt(const struct option *opt,
> const char *arg __maybe_unused,
> int unset __maybe_unused)
> {
> + *(bool *)opt->set = true;
hum, how does this set callgraph_set ?
shouldn't it be 'callgraph_set = true' instead?
jirka
> callchain_param.enabled = true;
>
> if (callchain_param.record_mode == CALLCHAIN_NONE)
> diff --git a/tools/perf/perf.h b/tools/perf/perf.h
> index 937b16a..9ba02e0 100644
> --- a/tools/perf/perf.h
> +++ b/tools/perf/perf.h
> @@ -52,6 +52,7 @@ struct record_opts {
> bool sample_weight;
> bool sample_time;
> bool sample_time_set;
> + bool callgraph_set;
> bool period;
> bool sample_intr_regs;
> bool running_time;
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2015-07-17 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 8:26 [PATCH RFC V4 0/4] per event callgrap and time support kan.liang
2015-07-16 8:26 ` [PATCH RFC V4 1/4] perf,tools: introduce callgraph_set for callgraph option kan.liang
2015-07-17 9:23 ` Jiri Olsa [this message]
2015-07-17 14:24 ` Liang, Kan
2015-07-16 8:26 ` [PATCH RFC V4 2/4] perf,tool: per-event time support kan.liang
2015-07-16 8:26 ` [PATCH RFC V4 3/4] perf,tool: per-event callgrap support kan.liang
2015-07-16 8:26 ` [PATCH RFC V4 4/4] perf,tests: Add tests to callgrap and time parse kan.liang
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=20150717092357.GA1057@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.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