public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	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: perf: unwind: target platform=x86 not supported was:  Re: [PATCH 1/2] perf evsel: Fix probing of precise_ip level for default cycles event
Date: Wed, 14 Jun 2017 11:47:29 -0300	[thread overview]
Message-ID: <20170614144729.GG32020@kernel.org> (raw)
In-Reply-To: <20170614141951.GA14162@krava>

Em Wed, Jun 14, 2017 at 04:19:51PM +0200, Jiri Olsa escreveu:
> 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@jouet linux]$ grep CONFIG_LIBUNWIND_X86 /tmp/build/perf/.config-detected
> > [acme@jouet 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?

amd64/x86_64, ubuntu, libunwind version 8, perhaps this version has a
problem? See the other message I replied to Ingo, added you to the CC.

- Arnaldo

  parent reply	other threads:[~2017-06-14 14:47 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
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 [this message]
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=20170614144729.GG32020@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=jolsa@kernel.org \
    --cc=jolsa@redhat.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