From: Taeung Song <treeze.taeung@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Borislav Petkov <bp@suse.de>,
Chandler Carruth <chandlerc@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Stephane Eranian <eranian@google.com>,
Wang Nan <wangnan0@huawei.com>,
Brendan Gregg <brendan.d.gregg@gmail.com>
Subject: Re: [PATCH 2/3] perf top: Support call-graph display options also
Date: Thu, 22 Oct 2015 22:57:35 +0900 [thread overview]
Message-ID: <E19FF97A-F5A0-4E75-B835-C651AD15AE8C@gmail.com> (raw)
In-Reply-To: <CAM9d7ciGyKSLi6W7U=T3ij1CuTvXT_QmMciG=Z-gavRUVeZH5g@mail.gmail.com>
Hi, Namhyung and Ingo
> On Oct 22, 2015, at 9:20 PM, Namhyung Kim <namhyung@kernel.org> wrote:
>
> On Thu, Oct 22, 2015 at 5:23 PM, Ingo Molnar <mingo@kernel.org> wrote:
>>
>> * Namhyung Kim <namhyung@kernel.org> wrote:
>>
>>> Currently 'perf top --call-graph' option is same as 'perf record'. But
>>> 'perf top' also need to receive display options in 'perf report'. To do
>>> that, change parse_callchain_report_opt() to allow record options too.
>>>
>>> Now perf top can receive display options like below:
>>>
>>> $ perf top --call-graph
>>> Error: option `call-graph' requires a value
>>>
>>> Usage: perf top [<options>]
>>>
>>> --call-graph
>>> <mode[,dump_size],output_type,min_percent[,print_limit],call_order[,branch]>
>>> setup and enables call-graph (stack chain/backtrace)
>>> recording: fp dwarf lbr, output_type (graph, flat,
>>> fractal, or none), min percent threshold, optional
>>> print limit, callchain order, key (function or
>>> address), add branches
>>
>> Yeah, so this fix is nice, and I think we should also do another patch to fix the
>> help text output to be the following:
>>
>> --call-graph
>> <record_mode[,record_size],print_style,limit[,print_limit],call_order[,sort_key]>
>>
>> Set up and enable call graph (call chain, stack backtrace) recording:
>>
>> record_mode: call graph recording mode (fp|dwarf|lbr)
>> record_size: if rec_mode == dwarf, maximum depth of stack recording (bytes),
>> default: 8192 bytes.
>> print_style: call graph printing style (graph|flat|fractal|none)
>> limit: minimum call graph inclusion threshold (percent)
>> print_limit: printing threshold (percent)
>> call_order: call graph order (caller|callee)
>> sort_key: sorting key (function|address|branch)
>>
>> Default: fp,graph,0.5,0.0,caller,function
>>
>> Note that this text evolved a bit over what I sent in my previous mail.
>
> OK. I'll cook a patch to improve help message like this as well as man page.
>
>
>>
>> Also note that I think we should sync up the perf config options to be the same as
>> the option name shortcuts used in this help text.
>
> Ah, good idea.
>
>>
>> Side note: to improve perf config usability, we should probably also recognize
>> underscores in perf config entries, i.e. the following variants should both work:
>>
>> print_percent = 1
>> print-percent = 1
>>
>> Right now only the second one will match.
>
> Taeung, could you consider fixing this in your config patchiest?
>
Sure, no problem.
I thought as below.
Even if one use a print_percent variable, it will be handled like print-percent.
Also if a user change print_percent variable by perf-config command,
print-percent variable will remain in perfconfig file.
(Because perf-config command will rewrite perfconfig file.)
Is anything wrong ?
Thanks,
Taeung
next prev parent reply other threads:[~2015-10-22 13:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 6:28 [PATCH 1/3] perf tools: Move callchain help messages to callchain.h Namhyung Kim
2015-10-22 6:28 ` [PATCH 2/3] perf top: Support call-graph display options also Namhyung Kim
2015-10-22 8:23 ` Ingo Molnar
2015-10-22 12:20 ` Namhyung Kim
2015-10-22 13:57 ` Taeung Song [this message]
2015-10-22 14:34 ` Namhyung Kim
2015-10-22 18:38 ` Arnaldo Carvalho de Melo
2015-10-23 8:31 ` [tip:perf/core] " tip-bot for Namhyung Kim
2015-10-22 6:28 ` [RFC/PATCH 3/3] perf tools: Defaults to 'caller' callchain order only if --children is enabled Namhyung Kim
2015-10-22 7:32 ` Ingo Molnar
2015-10-22 7:38 ` Namhyung Kim
2015-10-22 9:49 ` Brendan Gregg
2015-10-22 14:03 ` Arnaldo Carvalho de Melo
2015-11-02 23:59 ` Brendan Gregg
2015-10-22 12:21 ` Frederic Weisbecker
2015-10-22 7:45 ` [RFC/PATCH RESEND " Namhyung Kim
2015-10-22 18:38 ` Arnaldo Carvalho de Melo
2015-10-23 8:31 ` [tip:perf/core] " tip-bot for Namhyung Kim
2015-10-22 12:19 ` [RFC/PATCH 3/3] " Frederic Weisbecker
2015-10-22 14:13 ` Arnaldo Carvalho de Melo
2015-10-22 14:22 ` Namhyung Kim
2015-10-22 14:37 ` Arnaldo Carvalho de Melo
2015-10-22 15:51 ` Namhyung Kim
2015-10-22 16:21 ` Arnaldo Carvalho de Melo
2015-10-22 8:02 ` [PATCH 1/3] perf tools: Move callchain help messages to callchain.h Ingo Molnar
2015-10-22 12:13 ` Namhyung Kim
2015-10-22 14:17 ` Arnaldo Carvalho de Melo
2015-10-23 9:59 ` Ingo Molnar
2015-10-23 14:27 ` Arnaldo Carvalho de Melo
2015-10-23 16:40 ` Arnaldo Carvalho de Melo
2015-10-22 18:38 ` Arnaldo Carvalho de Melo
2015-10-23 8:30 ` [tip:perf/core] " tip-bot for Namhyung Kim
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=E19FF97A-F5A0-4E75-B835-C651AD15AE8C@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=bp@suse.de \
--cc=brendan.d.gregg@gmail.com \
--cc=chandlerc@gmail.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®