From: Adrian Hunter <adrian.hunter@intel.com>
To: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [BUG] perf: does not compile on ARM because of Intel PT code
Date: Tue, 01 Sep 2015 11:26:23 +0300 [thread overview]
Message-ID: <55E5612F.4030800@intel.com> (raw)
In-Reply-To: <CABPqkBR_zU6QYDq0Gbgf8QirkBW5-HDONujf2KHKLtGwC07cOQ@mail.gmail.com>
On 01/09/15 11:26, Stephane Eranian wrote:
> Hi,
>
> If you compile tip.git on ARM32 (or ARM64, I bet) you compile link time errors:
>
> libperf.a(libperf-in.o): In function `intel_pt_synth_branch_sample':
> /home/ubuntu/perfmon/linux/tools/perf/util/intel-pt.c:899: undefined
> reference to `tsc_to_perf_time'
> libperf.a(libperf-in.o): In function `intel_pt_synth_transaction_sample':
> /home/ubuntu/perfmon/linux/tools/perf/util/intel-pt.c:992: undefined
> reference to `tsc_to_perf_time'
> libperf.a(libperf-in.o): In function `intel_pt_synth_instruction_sample':
> /home/ubuntu/perfmon/linux/tools/perf/util/intel-pt.c:943: undefined
> reference to `tsc_to_perf_time'
> libperf.a(libperf-in.o): In function `intel_pt_process_event':
> /home/ubuntu/perfmon/linux/tools/perf/util/intel-pt.c:1484: undefined
> reference to `perf_time_to_tsc'
> libperf.a(libperf-in.o): In function `intel_pt_process_itrace_start':
> /home/ubuntu/perfmon/linux/tools/perf/util/intel-pt.c:1455: undefined
> reference to `perf_time_to_tsc'
> libperf.a(libperf-in.o): In function `intel_pt_process_switch':
> /home/ubuntu/perfmon/linux/tools/perf/util/intel-pt.c:1405: undefined
> reference to `perf_time_to_tsc'
> /home/ubuntu/perfmon/linux/tools/perf/util/intel-pt.c:1427: undefined
> reference to `perf_time_to_tsc'
> libperf.a(libperf-in.o): In function `intel_bts_process_event':
> /home/ubuntu/perfmon/linux/tools/perf/util/intel-bts.c:614: undefined
> reference to `perf_time_to_tsc'
>
> That's because if AUXTRACE is detected, it pulls in x86 specific stuff
> like intel-pt. This should
> be decoupled.
Ingo just pulled the fix for that a moment ago. Look for "perf tools: Fix
build on powerpc broken by pt/bts"
next prev parent reply other threads:[~2015-09-01 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 8:26 [BUG] perf: does not compile on ARM because of Intel PT code Stephane Eranian
2015-09-01 8:26 ` Adrian Hunter [this message]
2015-09-01 8:29 ` Stephane Eranian
2015-09-01 8:42 ` Ingo Molnar
2015-09-01 8:44 ` Stephane Eranian
2015-09-01 8:51 ` Stephane Eranian
2015-09-01 8:57 ` Ingo Molnar
2015-09-01 8:30 ` 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=55E5612F.4030800@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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