From: Ingo Molnar <mingo@elte.hu>
To: Arun Sharma <asharma@fb.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Tom Zanussi <tzanussi@gmail.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [RFC] Sort inclusive
Date: Tue, 6 Mar 2012 07:57:53 +0100 [thread overview]
Message-ID: <20120306065753.GB5100@elte.hu> (raw)
In-Reply-To: <20120305221253.GA30250@dev3310.snc6.facebook.com>
* Arun Sharma <asharma@fb.com> wrote:
> Some of our users have been asking for the ability to sort
> samples by inclusive time (time spent in the function + all of
> the callees in the callgraph).
If this feature gets mature enough I'd even suggest that we make
this the default output mode.
( Sidenote: the patched perf_evsel__add_hist_entry() function
seems a tad large now, it might make sense to factor out one
or two helper inline functions from it and thus clean up the
flow all around. )
Btw., assuming that you are profiling user-space applications
via call-chains, how do you deal with the lack of dwarf decoding
done by perf, in particular on 64-bit x86 systems where most
distros don't compile call-chains into libraries and
application? In what practical situations does that limitation
hinder you and what do you do about it - rebuild your apps with
frame pointers included?
Thanks,
Ingo
next prev parent reply other threads:[~2012-03-06 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 22:12 [RFC] Sort inclusive Arun Sharma
2012-03-05 23:41 ` Arun Sharma
2012-03-06 6:57 ` Ingo Molnar [this message]
2012-03-06 19:41 ` Arun Sharma
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=20120306065753.GB5100@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=asharma@fb.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tzanussi@gmail.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).