[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170614141951.GA14162@krava>
Date: Wed, 14 Jun 2017 16:19:51 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Jiri Olsa <jolsa@...nel.org>, Ingo Molnar <mingo@...nel.org>,
linux-kernel@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
David Ahern <dsahern@...il.com>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Wang Nan <wangnan0@...wei.com>
Subject: Re: perf: unwind: target platform=x86 not supported was: Re: [PATCH
1/2] perf evsel: Fix probing of precise_ip level for default cycles event
On Wed, Jun 14, 2017 at 10:52:42AM -0300, Arnaldo Carvalho de Melo wrote:
SNIP
>
> And what defines it is...
>
> tools/perf/util/libunwind/x86_32.c:#define REMOTE_UNWIND_LIBUNWIND
>
> (and a arm64 file, but lets leave that aside, seems unrelated to this
> case)
>
> That will get built by...
>
> tools/perf/util/Build:libperf-$(CONFIG_LIBUNWIND_X86) += libunwind/x86_32.o
>
> [acme@...et linux]$ grep CONFIG_LIBUNWIND_X86 /tmp/build/perf/.config-detected
> [acme@...et linux]$
>
> Ingo, are you doing something unusual as building a 32-bit perf to read a
> 62-bit perf.data file?
>
> Jiri, can you help here? Do you need more info?
hum, looks like local unwind support wasn't compiled in for some reason
Ingo, what's the arch of host and perf data?
thanks,
jirka
Powered by blists - more mailing lists