From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
Namhyung Kim <namhyung@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCHSET 0/5] perf tools: Speed up dwarf callchain post-unwinding for libunwind (v3)
Date: Thu, 2 Oct 2014 12:08:50 +0900 [thread overview]
Message-ID: <1412219335-17417-1-git-send-email-namhyung@kernel.org> (raw)
Hello,
This is v3 for libunwind callchain post processing speed up. It was
able to reduce 50% of processing time by using global cache provided
in libunwind. In this version, I decided to use the existing
callchain_param.record_mode instead of adding a new field in the
symbol_conf.
The patch 4 and 5 are just cleanups so that we can easily find out
that which part of code uses the thread->priv.
You can also get it from 'perf/callchain-unwind-v3' branch on my tree:
git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Thanks,
Namhyung
Namhyung Kim (5):
perf report: Set callchain_param.record_mode for future use
perf callchain: Create an address space per thread
perf callchain: Use global caching provided by libunwind
perf kvm: Use thread_{,_set}_priv helpers
perf trace: Use thread_{,_set}_priv helpers
tools/perf/builtin-kvm.c | 6 ++---
tools/perf/builtin-report.c | 6 +++++
tools/perf/builtin-trace.c | 16 ++++++-------
tools/perf/tests/dwarf-unwind.c | 3 +++
tools/perf/util/callchain.h | 2 ++
tools/perf/util/hist.h | 2 --
tools/perf/util/thread.c | 9 +++++++
tools/perf/util/unwind-libunwind.c | 48 ++++++++++++++++++++++++++++++++++----
tools/perf/util/unwind.h | 20 ++++++++++++++++
9 files changed, 94 insertions(+), 18 deletions(-)
--
2.1.0
next reply other threads:[~2014-10-02 3:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 3:08 Namhyung Kim [this message]
2014-10-02 3:08 ` [PATCH 1/5] perf report: Set callchain_param.record_mode for future use Namhyung Kim
2014-10-02 3:12 ` [PATCH v3.1 " Namhyung Kim
2014-10-02 13:46 ` Jiri Olsa
2014-10-02 3:08 ` [PATCH 2/5] perf callchain: Create an address space per thread Namhyung Kim
2014-10-02 3:08 ` [PATCH 3/5] perf callchain: Use global caching provided by libunwind Namhyung Kim
2014-10-02 3:08 ` [PATCH 4/5] perf kvm: Use thread_{,_set}_priv helpers Namhyung Kim
2014-10-02 3:08 ` [PATCH 5/5] perf trace: " Namhyung Kim
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=1412219335-17417-1-git-send-email-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®