From: Paolo Bonzini <pbonzini@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Brendan Gregg <bgregg@netflix.com>
Subject: Re: ping Re: [PATCH] perf script: Add stackcollapse.py script
Date: Fri, 15 Apr 2016 13:09:54 +0200 [thread overview]
Message-ID: <5710CC02.9020303@redhat.com> (raw)
In-Reply-To: <20160415105739.GA8595@krava.redhat.com>
On 15/04/2016 12:57, Jiri Olsa wrote:
>>> > > +# Input may be created and processed using:
>>> > > +#
>>> > > +# perf record -a -g -F 99 sleep 60
>>> > > +# perf script report stackcollapse > out.stacks-folded
>>> > > +#
>>> > > +# (perf script record stackcollapse works too).
> IIRC Namhyung added -g folded option recently for report
> so you could do:
>
> perf report -g folded --stdio
>
> however we dont seem to have it for perf script, so this might
> be useful until we add the --call-graph support into perf script
Thanks for the pointer. I think the output of "perf script -g folded"
would still be a bit different from what the flamegraph tool expects.
Something like
perf 13675 51165.817380: 1921 cycles:pp: native_write_cr2; do_nmi; end_repeat_nmi; ...
rather than this
perf;native_write_cr2;do_nmi;end_repeat_nmi;... 1921
which this script produces. The format that flamegraph expects is very
simple so that they can have converters for perf, stap, dtrace and others.
I'd be just as happy if perf looked for scripts into $HOME/.local. :) But
since it doesn't, this script can also be useful to demonstrate script access
to callchains.
Thanks,
Paolo
next prev parent reply other threads:[~2016-04-15 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 13:26 [PATCH] perf script: Add stackcollapse.py script Paolo Bonzini
2016-04-15 5:20 ` ping " Paolo Bonzini
2016-04-15 10:57 ` Jiri Olsa
2016-04-15 11:09 ` Paolo Bonzini [this message]
2016-05-20 11:01 ` Paolo Bonzini
2016-06-16 7:49 ` Jiri Olsa
2016-06-16 7:22 ` Paolo Bonzini
2016-06-16 7:49 ` Jiri Olsa
2016-06-16 9:26 ` Paolo Bonzini
2016-06-22 7:44 ` [tip:perf/core] " tip-bot for Paolo Bonzini
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=5710CC02.9020303@redhat.com \
--to=pbonzini@redhat.com \
--cc=acme@redhat.com \
--cc=bgregg@netflix.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.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