From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Brendan Gregg <bgregg@netflix.com>,
Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Alexei Starovoitov <ast@kernel.org>,
Andi Kleen <ak@linux.intel.com>, David Ahern <dsahern@gmail.com>,
Ekaterina Tumanova <tumanova@linux.vnet.ibm.com>,
He Kuang <hekuang@huawei.com>, Jean Delvare <jdelvare@suse.de>,
Jiri Olsa <jolsa@redhat.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Kan Liang <kan.liang@intel.com>,
linux-kbuild@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Michal Marek <mmarek@suse.com>, Pekka Enberg <penberg@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
pi3orama@163.com, Stephane Eranian <eranian@google.com>,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
Wang Nan <wangnan0@huawei.com>, Zefan Li <lizefan@huawei.com>
Subject: Re: [GIT PULL 00/10] perf/core improvements and fixes
Date: Tue, 21 Jun 2016 13:14:15 -0300 [thread overview]
Message-ID: <20160621161415.GA2797@redhat.com> (raw)
In-Reply-To: <2c189c43-81e8-4052-c62c-3b548b3eb32a@redhat.com>
Em Tue, Jun 21, 2016 at 12:08:47PM +0200, Paolo Bonzini escreveu:
> On 21/06/2016 05:11, Brendan Gregg wrote:
> >>> > > - Add stackcollapse.py script to help generating flame graphs (Paolo Bonzini)
> >> >
> >> > I think this is already done by '-g folded'. Please see:
> >> >
> >> > http://www.brendangregg.com/blog/2016-04-30/linux-perf-folded.html
> >> >
> > Pretty much. Two similar solutions were developed around the same
> > time. Although I have to use some awk to get "perf -g folded" in the
> > exact right format, and stackcollapse-perf.py does that directly.
>
> Yes, the idea for stackcollapse-perf.py was:
>
> - to do everything directly and emit "the right" format for the
> flamegraph tools. This however is a very minimal output, and it's not
> necessarily the best for perf in general.
>
> - to provide an example of visiting callgraphs from the scripting
> interface, since it's not really documented. From the commit message:
> "Add stackcollapse.py script as an example of parsing call chains, and
> also of using optparse to access command line options".
Yeah, agreed, its short, and it provides the output ready to be used, no
need for extra processing, up to the user to decide if one or the other
is more suitable to their needs.
As a bonus, it documents callgraphs in scripts, good deal :-)
- Arnaldo
next prev parent reply other threads:[~2016-06-21 16:14 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 22:23 [GIT PULL 00/10] perf/core improvements and fixes Arnaldo Carvalho de Melo
2016-06-20 22:23 ` [PATCH 01/10] perf tools: Find vdso with the consider of cross-platform Arnaldo Carvalho de Melo
2016-06-20 22:23 ` [PATCH 02/10] kbuild: List libelf-devel as an alternative Arnaldo Carvalho de Melo
2016-06-20 22:23 ` [PATCH 03/10] perf script: Fix documentation of '-f' when it should be '-F' Arnaldo Carvalho de Melo
2016-06-20 22:23 ` [PATCH 04/10] perf hists: Rename __hists__add_entry to hists__add_entry Arnaldo Carvalho de Melo
2016-06-20 22:23 ` [PATCH 05/10] perf tools: Remove some unused functions Arnaldo Carvalho de Melo
2016-06-20 22:23 ` [PATCH 06/10] perf tools: Remove --perf-dir and --work-dir Arnaldo Carvalho de Melo
2016-06-20 22:23 ` [PATCH 07/10] perf llvm: Allow dump llvm output object file using llvm.dump-obj Arnaldo Carvalho de Melo
2016-06-20 22:23 ` [PATCH 08/10] perf record: Add --dry-run option to check cmdline options Arnaldo Carvalho de Melo
2016-06-20 22:23 ` [PATCH 09/10] perf evsel: Fix write_backwards fallback Arnaldo Carvalho de Melo
2016-06-20 22:23 ` [PATCH 10/10] perf script: Add stackcollapse.py script Arnaldo Carvalho de Melo
2016-06-21 18:36 ` Brendan Gregg
2016-06-21 20:19 ` Arnaldo Carvalho de Melo
2016-06-21 2:18 ` [GIT PULL 00/10] perf/core improvements and fixes Namhyung Kim
2016-06-21 3:11 ` Brendan Gregg
2016-06-21 10:08 ` Paolo Bonzini
2016-06-21 16:14 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-16 20:20 Arnaldo Carvalho de Melo
2017-08-17 7:45 ` Ingo Molnar
2017-05-03 13:58 Arnaldo Carvalho de Melo
2017-05-03 17:30 ` Ingo Molnar
2017-01-17 16:06 Arnaldo Carvalho de Melo
2017-01-18 9:09 ` Ingo Molnar
2016-12-07 16:53 Arnaldo Carvalho de Melo
2016-12-07 18:17 ` Ingo Molnar
2016-05-25 21:34 Arnaldo Carvalho de Melo
2016-04-01 21:56 Arnaldo Carvalho de Melo
2016-04-06 6:47 ` Ingo Molnar
2016-02-16 20:34 Arnaldo Carvalho de Melo
2016-02-17 7:39 ` Ingo Molnar
2015-11-28 1:22 Arnaldo Carvalho de Melo
2015-11-28 9:50 ` Ingo Molnar
2015-11-29 13:16 ` Namhyung Kim
2015-08-28 18:06 Arnaldo Carvalho de Melo
2015-08-31 8:28 ` Ingo Molnar
2015-07-30 16:16 Arnaldo Carvalho de Melo
2015-07-31 8:04 ` Ingo Molnar
2015-07-31 13:30 ` Arnaldo Carvalho de Melo
2015-06-16 18:21 Arnaldo Carvalho de Melo
2015-01-29 20:23 Arnaldo Carvalho de Melo
2015-01-30 18:28 ` Ingo Molnar
2014-12-22 15:29 Arnaldo Carvalho de Melo
2014-09-26 20:19 Arnaldo Carvalho de Melo
2014-09-27 7:20 ` Ingo Molnar
2014-04-08 18:00 Jiri Olsa
[not found] ` <8738hnk3dg.fsf@tassilo.jf.intel.com>
[not found] ` <CAM9d7ciP4tLUmR-soEKH3nf6=XC5evKGfuQW1fUGA8Z42U3xCg@mail.gmail.com>
2014-04-09 5:31 ` Ingo Molnar
2013-11-14 20:25 Arnaldo Carvalho de Melo
2013-11-15 6:38 ` Ingo Molnar
2013-11-11 20:22 Arnaldo Carvalho de Melo
2013-11-05 20:09 Arnaldo Carvalho de Melo
2013-11-06 5:31 ` Ingo Molnar
2013-09-02 20:56 Arnaldo Carvalho de Melo
2013-09-03 5:49 ` Ingo Molnar
2013-02-14 21:44 Arnaldo Carvalho de Melo
2013-02-15 15:39 ` Ingo Molnar
2011-12-20 19:18 Arnaldo Carvalho de Melo
2011-12-20 19:33 ` Ingo Molnar
2010-08-06 1:46 Arnaldo Carvalho de Melo
2010-08-06 7:00 ` Ingo Molnar
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=20160621161415.GA2797@redhat.com \
--to=acme@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ast@kernel.org \
--cc=bgregg@netflix.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=hekuang@huawei.com \
--cc=jdelvare@suse.de \
--cc=jolsa@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.com \
--cc=namhyung@kernel.org \
--cc=pbonzini@redhat.com \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=pi3orama@163.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=tumanova@linux.vnet.ibm.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 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).