From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH 1/2] perf evsel: Fix probing of precise_ip level for default cycles event
Date: Wed, 14 Jun 2017 10:29:47 -0300 [thread overview]
Message-ID: <20170614132947.GC32020@kernel.org> (raw)
In-Reply-To: <20170614054500.exocsybw2qkug5tn@gmail.com>
Em Wed, Jun 14, 2017 at 07:45:01AM +0200, Ingo Molnar escreveu:
> triton:~/tip> perf report --stdio
> unwind: target platform=x86 is not supported
> unwind: target platform=x86 is not supported
> unwind: target platform=x86 is not supported
> unwind: target platform=x86 is not supported
> unwind: target platform=x86 is not supported
> unwind: target platform=x86 is not supported
> unwind: target platform=x86 is not supported
> unwind: target platform=x86 is not supported
> # ========
> # captured on: Wed Jun 14 07:34:42 2017
> # hostname : triton
> # os release : 4.10.0-23-generic
> # perf version : 4.12.rc5.g9688eb
> # arch : x86_64
> # nrcpus online : 12
> # nrcpus avail : 12
> # cpudesc : Intel(R) Core(TM) i7-4960X CPU @ 3.60GHz
> # cpuid : GenuineIntel,6,62,4
> # total memory : 65917012 kB
> # cmdline : /home/mingo/bin/perf record /home/mingo/hackbench 10
> let me know if you need more info.
>
> Btw., note that there's also this warning:
>
> unwind: target platform=x86 is not supported
>
> (but that's unrelated to this commit.)
Ok, what distro? Do you have libunwind-devel installed? I couldn't
reproduce this one here with/without it installed, to test I build it
with:
make ARCH=x86_64 O=/tmp/build/perf -C tools/perf install-bin
and without that ARCH= setting, then I record with:
perf record --call-graph dwarf -a sleep 2
and try what you said emitted that warning:
perf report --stdio
- Arnaldo
next prev parent reply other threads:[~2017-06-14 13:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 23:23 [GIT PULL 0/2] perf/urgent fixes for 4.12 Arnaldo Carvalho de Melo
2017-06-13 23:23 ` [PATCH 1/2] perf evsel: Fix probing of precise_ip level for default cycles event Arnaldo Carvalho de Melo
2017-06-14 5:45 ` Ingo Molnar
2017-06-14 10:44 ` Arnaldo Carvalho de Melo
2017-06-14 10:51 ` Ingo Molnar
2017-06-14 10:57 ` Arnaldo Carvalho de Melo
2017-06-14 13:55 ` Ingo Molnar
2017-06-14 14:44 ` Arnaldo Carvalho de Melo
2017-06-14 13:29 ` Arnaldo Carvalho de Melo [this message]
2017-06-14 13:52 ` perf: unwind: target platform=x86 not supported was: " Arnaldo Carvalho de Melo
2017-06-14 14:19 ` Jiri Olsa
2017-06-14 14:31 ` Jiri Olsa
2017-06-14 14:47 ` Arnaldo Carvalho de Melo
2017-06-14 14:06 ` Ingo Molnar
2017-06-14 14:46 ` Arnaldo Carvalho de Melo
2017-06-14 19:12 ` Arnaldo Carvalho de Melo
2017-06-13 23:23 ` [PATCH 2/2] perf tools: Fix build with ARCH=x86_64 Arnaldo Carvalho de Melo
2017-06-14 5:33 ` [GIT PULL 0/2] perf/urgent fixes for 4.12 Ingo Molnar
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=20170614132947.GC32020@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dsahern@gmail.com \
--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