linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sam Liao <phyomh@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	acme@redhat.com, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] Add inverted call graph report support to perf tool
Date: Fri, 6 May 2011 10:54:38 +0200	[thread overview]
Message-ID: <20110506085438.GA928@elte.hu> (raw)
In-Reply-To: <AANLkTimaxPJCkA3TuDQKCvDXtqTrUb8vyrNqRRSzvYwb@mail.gmail.com>


* Sam Liao <phyomh@gmail.com> wrote:

> > It depends if you select reverse callchain or not:
> >
> > $ perf report -s caller
> >
> > That will report main and kernel_thread as hists, and regular callee -> caller callchains.
> > Hence under main hist, you'll a lot of callchain starting from random points and all
> > ending in main!
> >
> > $ perf report -s caller -g caller
> >
> > That will report main and kernel_thread as hists, with callchains starting from
> > main under main.
> >
> > It becomes interesting when you want more granularity with -s caller,dso if we bring a way
> > to push forward the entrypoint one day. I suspect even more sorting combinations are
> > going to be interesting.
> >
> 
> Thanks for clarification. I'll try to come up with patches as you talked.

I'm wondering, is there any progress with this feature? Having sysprof-alike 
reverse ordering for call chains is a really powerful form of visualization 
IMO.

Thanks,

	Ingo

  reply	other threads:[~2011-05-06  8:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 13:43 [PATCH] Add inverted call graph report support to perf tool Sam Liao
2011-03-07 18:06 ` Frederic Weisbecker
2011-03-08  8:59   ` Sam Liao
2011-03-10  2:43     ` Frederic Weisbecker
2011-03-10  6:48       ` Ingo Molnar
2011-03-11 10:51         ` Frederic Weisbecker
2011-03-11 14:45           ` Arnaldo Carvalho de Melo
2011-03-10 14:32       ` Sam Liao
2011-03-11 11:57         ` Frederic Weisbecker
2011-03-11 12:07           ` Frederic Weisbecker
2011-03-12 14:59           ` Sam Liao
2011-05-06  8:54             ` Ingo Molnar [this message]
2011-03-12  1:31 ` 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=20110506085438.GA928@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=phyomh@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).