From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com, tmricht@linux.ibm.com
Subject: Re: [PATCH] perf report: Fix no libunwind compiled warning break s390 issue
Date: Wed, 8 Jan 2020 21:02:02 +0800 [thread overview]
Message-ID: <7b88fdcc-9603-d3e1-d43b-b8fb8b394f70@linux.intel.com> (raw)
In-Reply-To: <20200108102708.GC360164@krava>
On 1/8/2020 6:27 PM, Jiri Olsa wrote:
> On Wed, Jan 08, 2020 at 03:17:45AM +0800, Jin Yao wrote:
>> Commit 800d3f561659 ("perf report: Add warning when libunwind not compiled in")
>> breaks the s390 platform. S390 uses libdw-dwarf-unwind for call chain
>> unwinding and had no support for libunwind.
>>
>> So the warning "Please install libunwind development packages during the perf build."
>> caused the confusion even if the call-graph is displayed correctly.
>>
>> This patch adds checking for HAVE_DWARF_SUPPORT, which is set when
>> libdw-dwarf-unwind is compiled in.
>>
>> Fixes: 800d3f561659 ("perf report: Add warning when libunwind not compiled in")
>>
>> Reviewed-by: Thomas Richter <tmricht@linux.ibm.com>
>> Tested-by: Thomas Richter <tmricht@linux.ibm.com>
>> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
>
> perfect, I have the same change prepared for sending, but it's
> together with making libdw default dwarf unwinder, which I'm still
> not sure we want to do, so it all got posponed ;-)
> > would you guys be ok with that? with having libdw picked up as
default dwarf unwinder..
>
I've roughly compared the performance between libunwind-dev and
libdw-dev. While in my test (on KBL desktop), for the same perf report
command-line, it looks the perf built with libunwind-dev is much faster
than the perf built with libdw-dev.
The command line is as following:
perf record --call-graph dwarf ./div
perf report -g graph --stdio
Maybe you give it a try. :)
> for the patch:
>
> Acked-by: Jiri Olsa <jolsa@redhat.com>
>
Thanks for reviewing the patch.
Thanks
Jin Yao
> thanks,
> jirka
>
>> ---
>> tools/perf/builtin-report.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
>> index de988589d99b..66cd97cc8b92 100644
>> --- a/tools/perf/builtin-report.c
>> +++ b/tools/perf/builtin-report.c
>> @@ -412,10 +412,10 @@ static int report__setup_sample_type(struct report *rep)
>> PERF_SAMPLE_BRANCH_ANY))
>> rep->nonany_branch_mode = true;
>>
>> -#ifndef HAVE_LIBUNWIND_SUPPORT
>> +#if !defined(HAVE_LIBUNWIND_SUPPORT) && !defined(HAVE_DWARF_SUPPORT)
>> if (dwarf_callchain_users) {
>> - ui__warning("Please install libunwind development packages "
>> - "during the perf build.\n");
>> + ui__warning("Please install libunwind or libdw "
>> + "development packages during the perf build.\n");
>> }
>> #endif
>>
>> --
>> 2.17.1
>>
>
next prev parent reply other threads:[~2020-01-08 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 19:17 [PATCH] perf report: Fix no libunwind compiled warning break s390 issue Jin Yao
2020-01-08 10:27 ` Jiri Olsa
2020-01-08 13:02 ` Jin, Yao [this message]
2020-01-08 14:35 ` Jiri Olsa
2020-01-20 8:27 ` [tip: perf/core] " tip-bot2 for Jin Yao
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=7b88fdcc-9603-d3e1-d43b-b8fb8b394f70@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.com \
--cc=yao.jin@intel.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