From: tip-bot for Andi Kleen <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, acme@redhat.com,
ak@linux.intel.com, mingo@kernel.org, tglx@linutronix.de,
hpa@zytor.com
Subject: [tip:perf/core] perf report: In branch stack mode use address history sorting
Date: Sun, 7 Dec 2014 22:53:42 -0800 [thread overview]
Message-ID: <tip-09a6a1b07e5a579ef770d9728f5b158408c73c23@git.kernel.org> (raw)
In-Reply-To: <1416275935-20971-1-git-send-email-andi@firstfloor.org>
Commit-ID: 09a6a1b07e5a579ef770d9728f5b158408c73c23
Gitweb: http://git.kernel.org/tip/09a6a1b07e5a579ef770d9728f5b158408c73c23
Author: Andi Kleen <ak@linux.intel.com>
AuthorDate: Mon, 17 Nov 2014 17:58:54 -0800
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Mon, 1 Dec 2014 20:00:31 -0300
perf report: In branch stack mode use address history sorting
Enable CCKEY_ADDRESS address history sorting with --branch-history.
This makes get_srcline display the source lines correctly, otherwise all
history entries for a function a hunked into one.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Link: http://lkml.kernel.org/r/1416275935-20971-1-git-send-email-andi@firstfloor.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/builtin-report.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
index fb272ff..3936760 100644
--- a/tools/perf/builtin-report.c
+++ b/tools/perf/builtin-report.c
@@ -761,6 +761,7 @@ repeat:
symbol_conf.cumulate_callchain = false;
}
if (branch_call_mode) {
+ callchain_param.key = CCKEY_ADDRESS;
callchain_param.branch_callstack = 1;
symbol_conf.use_callchain = true;
callchain_register_param(&callchain_param);
prev parent reply other threads:[~2014-12-08 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 1:58 [PATCH 1/2] perf, tools: " Andi Kleen
2014-11-18 1:58 ` [PATCH 2/2] perf, tools: Remove use of BUILD_BUG_ON Andi Kleen
2014-12-08 6:53 ` tip-bot for Andi Kleen [this message]
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=tip-09a6a1b07e5a579ef770d9728f5b158408c73c23@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®