From: Milian Wolff <milian.wolff@kdab.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: "Arnaldo Carvalho de Melo" <acme@kernel.org>,
linux-perf-users@vger.kernel.org, "Jiri Olsa" <jolsa@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: [PATCH] perf report: Support caller callchain order when using DWARF unwinder.
Date: Tue, 03 Nov 2015 12:25:39 +0100 [thread overview]
Message-ID: <1709816.RSlVQ2aJOf@milian-kdab2> (raw)
In-Reply-To: <20151103073711.GB23878@krava.brq.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
On Tuesday, November 3, 2015 8:37:11 AM CET Jiri Olsa wrote:
> On Fri, Oct 09, 2015 at 07:29:34PM +0200, Milian Wolff wrote:
>
> SNIP
>
> > > ;-)
> > >
> > > any chance this could be done also for util/unwind-libdw.c ?
> >
> > That patch looks much better than mine. I'll try it out later next week
> > and
> > will also have a look at util/unwind-libdw.c. Question: How can I test the
> > behavior of the latter? Do I need to uninstall libunwind, or can I change
> > the unwinder at runtime somehow (env var?).
>
> It's either libunwind or libdw compiled in, so I'd suggest
> generic test (see below) and compile with make variables
> NO_LIBUNWIND=1 or NO_LIBDW_DWARF_UNWIND=1 to get desired
> unwinder compiled in
>
> > Also, are there unit tests for this behavior somewhere?
>
> please check tests/dwarf-unwind.c, I think you can add similar test
OK, I'll try to find the time to test this later this week. I have also some
more on my todo list regarding documentation and testing. If you don't hear
back from me though, I'd appreciate if someone could adopt this patch and make
sure it gets integrated.
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-03 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 15:16 [PATCH] perf report: Support caller callchain order when using DWARF unwinder Milian Wolff
2015-10-04 20:38 ` Arnaldo Carvalho de Melo
2015-10-05 11:08 ` Jiri Olsa
2015-10-09 17:29 ` Milian Wolff
2015-11-02 21:19 ` Arnaldo Carvalho de Melo
2015-11-03 7:33 ` Jiri Olsa
2015-11-03 12:06 ` Arnaldo Carvalho de Melo
2015-11-03 12:54 ` Milian Wolff
2015-11-03 14:28 ` Arnaldo Carvalho de Melo
2015-11-03 14:30 ` Arnaldo Carvalho de Melo
2015-11-03 14:32 ` Jiri Olsa
2015-11-03 15:11 ` Arnaldo Carvalho de Melo
2015-11-03 7:37 ` Jiri Olsa
2015-11-03 11:25 ` 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=1709816.RSlVQ2aJOf@milian-kdab2 \
--to=milian.wolff@kdab.com \
--cc=acme@kernel.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.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