From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCHSET 0/5] perf tools: Speed up dwarf callchain post-unwinding for libunwind (v4)
Date: Mon, 13 Oct 2014 20:11:58 +0200 [thread overview]
Message-ID: <20141013181158.GA28191@krava.redhat.com> (raw)
In-Reply-To: <1412556363-26229-1-git-send-email-namhyung@kernel.org>
On Mon, Oct 06, 2014 at 09:45:58AM +0900, Namhyung Kim wrote:
> Hello,
>
> This is v4 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-v4' 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
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
next prev parent reply other threads:[~2014-10-13 18:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 0:45 [PATCHSET 0/5] perf tools: Speed up dwarf callchain post-unwinding for libunwind (v4) Namhyung Kim
2014-10-06 0:45 ` [PATCH 1/5] perf report: Set callchain_param.record_mode for future use Namhyung Kim
2014-10-16 5:23 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2014-10-06 0:46 ` [PATCH 2/5] perf callchain: Create an address space per thread Namhyung Kim
2014-10-16 5:23 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2014-10-06 0:46 ` [PATCH 3/5] perf callchain: Use global caching provided by libunwind Namhyung Kim
2014-10-30 6:39 ` [tip:perf/core] " tip-bot for Namhyung Kim
2014-10-06 0:46 ` [PATCH 4/5] perf kvm: Use thread_{,_set}_priv helpers Namhyung Kim
2014-10-16 5:24 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2014-10-06 0:46 ` [PATCH 5/5] perf trace: " Namhyung Kim
2014-10-16 5:24 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2014-10-13 18:11 ` Jiri Olsa [this message]
2014-10-14 21:08 ` [PATCHSET 0/5] perf tools: Speed up dwarf callchain post-unwinding for libunwind (v4) Arnaldo Carvalho de Melo
2014-10-15 19:24 ` Arnaldo Carvalho de Melo
2014-10-15 20:06 ` Arnaldo Carvalho de Melo
2014-10-16 13:14 ` Namhyung Kim
2014-10-22 1:34 ` Namhyung Kim
2014-10-22 1:50 ` Arnaldo Carvalho de Melo
2014-10-23 23:35 ` Arnaldo Carvalho de Melo
2014-10-24 0:44 ` Namhyung Kim
2014-10-24 1:56 ` Arnaldo Carvalho de Melo
2014-10-24 2:37 ` 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=20141013181158.GA28191@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.