From: Milian Wolff <milian.wolff@kdab.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>,
Jan Kratochvil <jkratoch@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH 0/3] perf tools DWARF libunwind: Add callchain order support
Date: Sun, 22 Nov 2015 20:13:03 +0100 [thread overview]
Message-ID: <1995578.CCVFM6QIUW@agathebauer> (raw)
In-Reply-To: <20151119191037.GF29361@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Donnerstag, 19. November 2015 16:10:37 CET Arnaldo Carvalho de Melo wrote:
> Em Tue, Nov 17, 2015 at 04:05:36PM +0100, Jiri Olsa escreveu:
> > hi,
> > as reported by Milian, currently for DWARF unwind (both libdw
> > and libunwind) we display callchain in callee order only.
>
> Applied the latest versions, please check my perf/core branch to check
> that all is there as you expect.
Sorry for the late reply. I've just tested the current code in perf/core -
works like a charm! Many thanks to Jiri for improving my initial take on this
problem and also getting it fixed for libdw. Much appreciated!
Cheers
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
prev parent reply other threads:[~2015-11-22 19:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 15:05 [PATCH 0/3] perf tools DWARF libunwind: Add callchain order support Jiri Olsa
2015-11-17 15:05 ` [PATCH 1/3] perf tools: Move initial entry call into get_entries function Jiri Olsa
2015-11-26 8:18 ` [tip:perf/core] perf callchain: " tip-bot for Jiri Olsa
2015-11-17 15:05 ` [PATCH 2/3] perf tools: Add callchain order support for libunwind DWARF unwinder Jiri Olsa
2015-11-18 4:13 ` Wangnan (F)
2015-11-18 5:41 ` Namhyung Kim
2015-11-18 7:26 ` Wangnan (F)
2015-11-22 15:27 ` Namhyung Kim
2015-11-18 8:25 ` Jiri Olsa
2015-11-18 9:25 ` Namhyung Kim
2015-11-18 8:26 ` Jiri Olsa
2015-11-18 7:52 ` [PATCHv2 " Jiri Olsa
2015-11-18 9:29 ` Wangnan (F)
2015-11-26 8:18 ` [tip:perf/core] perf callchain: Add " tip-bot for Jiri Olsa
2015-11-18 7:54 ` [PATCH 2/3] perf tools: Add callchain " Jiri Olsa
2015-11-18 7:59 ` Wangnan (F)
2015-11-18 8:12 ` Jiri Olsa
2015-11-17 15:05 ` [PATCH 3/3] perf test: Add callchain order setup for DWARF unwinder test Jiri Olsa
2015-11-26 8:19 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-11-18 4:22 ` [PATCH 0/3] perf tools DWARF libunwind: Add callchain order support Wangnan (F)
2015-11-19 11:22 ` [PATCH 4/3] perf tools: Add callchain order support for libdw DWARF unwinder Jiri Olsa
2015-11-19 12:10 ` Wangnan (F)
2015-11-19 12:18 ` Wangnan (F)
2015-11-19 13:01 ` [PATCHv2 " Jiri Olsa
2015-11-26 8:19 ` [tip:perf/core] perf callchain: Add " tip-bot for Jiri Olsa
2015-11-19 19:10 ` [PATCH 0/3] perf tools DWARF libunwind: Add callchain order support Arnaldo Carvalho de Melo
2015-11-20 8:38 ` Jiri Olsa
2015-11-22 19:13 ` Milian Wolff [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=1995578.CCVFM6QIUW@agathebauer \
--to=milian.wolff@kdab.com \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jkratoch@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.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