linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Milian Wolff <milian.wolff@kdab.com>
Cc: Ben Redelings <benjamin.redelings@gmail.com>,
	linux-perf-users@vger.kernel.org
Subject: Re: Inverted call-graph broken?
Date: Mon, 2 Nov 2015 14:31:01 -0300	[thread overview]
Message-ID: <20151102173101.GQ2923@kernel.org> (raw)
In-Reply-To: <1674883.ENQNaJOMdu@agathebauer>

Em Sun, Nov 01, 2015 at 03:09:45PM +0100, Milian Wolff escreveu:
> On Samstag, 31. Oktober 2015 09:25:39 CET Ben Redelings wrote:
> >      I've been using perf with '--call-graph=dwarf' -- very useful! I'd
> > like to view call graphs in 'perf report' in "inverted" order. Adding
> > '-G' to 'perf report' appears to have no effect, though. (Also
> > '--call-graph=fractal,caller' has no effect.)  Am I missing something
> > obvious?
> 
> This was broken and only recently got fixed by me and Jiri.
> 
> http://article.gmane.org/gmane.linux.kernel.perf.user/2279
> 
> Afaik, the patch has not yet been included upstream though. Arnaldo, can you 
> take Jiri's patch, or is there still something left to be done?

I'll check, but please post the title of the message, the gmane link
above isn't working for me, produces:

"Gmane 	weft didn't produce an output."

A Message-Id would be even better.

- Arnaldo

  reply	other threads:[~2015-11-02 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 16:25 "perf script" broken with --call-graph=dwarf on recent kernels? Ben Redelings
2015-08-18  7:05 ` Jiri Olsa
2015-08-18 18:28   ` Ben Redelings
2015-10-31 13:25 ` Inverted call-graph broken? Ben Redelings
2015-11-01 14:09   ` Milian Wolff
2015-11-02 17:31     ` Arnaldo Carvalho de Melo [this message]
2015-11-02 18:29       ` Milian Wolff

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=20151102173101.GQ2923@kernel.org \
    --to=acme@kernel.org \
    --cc=benjamin.redelings@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=milian.wolff@kdab.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).