linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, namhyung@kernel.org,
	acme@kernel.org, mingo@kernel.org, peterz@infradead.org
Subject: Re: Implement lbr-as-callgraph v9
Date: Mon, 11 Aug 2014 11:52:18 +0200	[thread overview]
Message-ID: <20140811095218.GA20085@krava.brq.redhat.com> (raw)
In-Reply-To: <1406827029-7991-1-git-send-email-andi@firstfloor.org>

On Thu, Jul 31, 2014 at 10:17:00AM -0700, Andi Kleen wrote:
> [Forward ported to latest tip/perf/core]
> [Even more review feedback and some bugs addressed.]
> [Only port to changes in perf/core. No other changes.]
> [Rebase to latest perf/core]
> [Another rebase. No changes]
> 
> This patchkit implements lbr-as-callgraphs in per freport,
> as an alternative way to present LBR information.
> 
> Current perf report does a histogram over the branch edges,
> which is useful to look at basic blocks, but doesn't tell
> you anything about the larger control flow behaviour.
> 
> This patchkit adds a new option --branch-history that
> adds the branch paths to the callgraph history instead.
> 
> This allows to reason about individual branch paths leading
> to specific samples.
> 
> Also available at
> git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc perf/lbr-callgraph4

hi,
does the branch contain the v9?

thanks,
jirka

  parent reply	other threads:[~2014-08-11  9:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 17:17 Implement lbr-as-callgraph v9 Andi Kleen
2014-07-31 17:17 ` [PATCH 1/9] perf, tools: Support handling complete branch stacks as histograms Andi Kleen
2014-07-31 17:17 ` [PATCH 2/9] perf, tools: Add --branch-history option to report Andi Kleen
2014-07-31 17:17 ` [PATCH 3/9] perf, tools: Enable printing the srcline in the history Andi Kleen
2014-07-31 17:17 ` [PATCH 4/9] perf, tools: Only print base source file for srcline Andi Kleen
2014-07-31 17:17 ` [PATCH 5/9] perf, tools: Support source line numbers in annotate Andi Kleen
2014-07-31 17:17 ` [PATCH 6/9] perf, tools: Fix srcline sort key output to use width Andi Kleen
2014-07-31 17:17 ` [PATCH 7/9] tools, perf: Make get_srcline fall back to sym+offset Andi Kleen
2014-07-31 17:17 ` [PATCH 8/9] tools, perf: Make srcline output address with -v Andi Kleen
2014-07-31 17:17 ` [PATCH 9/9] tools, perf: Add asprintf replacement Andi Kleen
2014-08-11  9:52 ` Jiri Olsa [this message]
2014-08-11 16:40   ` Implement lbr-as-callgraph v9 Andi Kleen
2014-08-12 13:50 ` Jiri Olsa
2014-08-12 20:55   ` Andi Kleen
2014-08-13  7:24     ` Jiri Olsa
2014-08-13 18:24       ` Andi Kleen
2014-08-14 10:40         ` Jiri Olsa
2014-09-15 23:54 Andi Kleen

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=20140811095218.GA20085@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).