From: Ingo Molnar <mingo@kernel.org>
To: tglx@linutronix.de, bp@suse.de, wangnan0@huawei.com,
dsahern@gmail.com, hpa@zytor.com, namhyung@kernel.org,
linux-kernel@vger.kernel.org, acme@redhat.com, jolsa@redhat.com,
chandlerc@gmail.com, adrian.hunter@intel.com,
a.p.zijlstra@chello.nl, eranian@google.com,
brendan.d.gregg@gmail.com, fweisbec@gmail.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf tools: Improve call graph documents and help messages
Date: Fri, 23 Oct 2015 11:03:59 +0200 [thread overview]
Message-ID: <20151023090359.GA22437@gmail.com> (raw)
In-Reply-To: <tip-76a26549eb367f683fbb394b7246bef5dc665f8c@git.kernel.org>
* tip-bot for Namhyung Kim <tipbot@zytor.com> wrote:
> Commit-ID: 76a26549eb367f683fbb394b7246bef5dc665f8c
> Gitweb: http://git.kernel.org/tip/76a26549eb367f683fbb394b7246bef5dc665f8c
> Author: Namhyung Kim <namhyung@kernel.org>
> AuthorDate: Thu, 22 Oct 2015 23:28:32 +0900
> Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
> CommitDate: Thu, 22 Oct 2015 16:23:19 -0300
>
> perf tools: Improve call graph documents and help messages
>
> The --call-graph option is complex so we should provide better guide for
> users. Also change help message to be consistent with config option
> names. Now perf top will show help like below:
>
> $ perf top --call-graph
> Error: option `call-graph' requires a value
>
> Usage: perf top [<options>]
>
> --call-graph <record_mode[,record_size],print_type,threshold[,print_limit],order,sort_key[,branch]>
> setup and enables call-graph (stack chain/backtrace):
>
> record_mode: call graph recording mode (fp|dwarf|lbr)
> record_size: if record_mode is 'dwarf', max size of stack recording (<bytes>)
> default: 8192 (bytes)
> print_type: call graph printing style (graph|flat|fractal|none)
> threshold: minimum call graph inclusion threshold (<percent>)
> print_limit: maximum number of call graph entry (<number>)
> order: call graph order (caller|callee)
> sort_key: call graph sort key (function|address)
> branch: include last branch info to call graph (branch)
Btw., how is the last line to be interpreted? Is the 'branch' value 0/1? If yes
then the text should probably say so? Or does the string 'branch' have to be used?
Thanks,
Ingo
next prev parent reply other threads:[~2015-10-23 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 14:28 [PATCH 1/2] perf tools: Setup pager when printing usage and help Namhyung Kim
2015-10-22 14:28 ` [PATCH 2/2] perf tools: Improve call graph documents and help messages Namhyung Kim
2015-10-22 14:46 ` Arnaldo Carvalho de Melo
2015-10-22 16:05 ` Namhyung Kim
2015-10-22 16:26 ` Arnaldo Carvalho de Melo
2015-10-22 16:28 ` Frederic Weisbecker
2015-10-22 18:37 ` Arnaldo Carvalho de Melo
2015-10-23 8:31 ` [tip:perf/core] " tip-bot for Namhyung Kim
2015-10-23 9:03 ` Ingo Molnar [this message]
2015-10-24 15:52 ` Namhyung Kim
2015-10-25 9:19 ` Ingo Molnar
2015-10-22 14:41 ` [PATCH 1/2] perf tools: Setup pager when printing usage and help Arnaldo Carvalho de Melo
2015-10-22 15:58 ` 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=20151023090359.GA22437@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--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=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--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.