From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Subject: [PATCH 2/2] perf tools: Make NO_AUXTRACE default for non-x86 architectures
Date: Tue, 25 Aug 2015 13:42:28 +0300 [thread overview]
Message-ID: <1440499348-15629-2-git-send-email-adrian.hunter@intel.com> (raw)
In-Reply-To: <1440499348-15629-1-git-send-email-adrian.hunter@intel.com>
Currently the AUXTRACE infrastructure is only used by Intel PT
and Intel BTS but is compiled into all architectures to support
the ability to process a perf.data file (including one containing
Intel PT or Intel BTS data) from any architecture on any other
architecture.
Generally people don't want that ability with respect to AUXTRACE
by default.
Make the build option NO_AUXTRACE the default for non-x86
architectures. To build with AUXTRACE on those architectures
use NO_AUXTRACE=0.
The build-test is updated accordingly.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
tools/perf/config/Makefile | 8 ++++++++
tools/perf/tests/make | 2 ++
2 files changed, 10 insertions(+)
diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile
index 827557fc7511..ddc3b64fdad2 100644
--- a/tools/perf/config/Makefile
+++ b/tools/perf/config/Makefile
@@ -621,6 +621,14 @@ ifdef LIBBABELTRACE
endif
ifndef NO_AUXTRACE
+ ifneq ($(ARCH),x86)
+ NO_AUXTRACE := 1
+ else
+ NO_AUXTRACE := 0
+ endif
+endif
+
+ifeq ($(NO_AUXTRACE), 0)
$(call detected,CONFIG_AUXTRACE)
CFLAGS += -DHAVE_AUXTRACE_SUPPORT
endif
diff --git a/tools/perf/tests/make b/tools/perf/tests/make
index ba31c4bd441d..977ded210de2 100644
--- a/tools/perf/tests/make
+++ b/tools/perf/tests/make
@@ -44,6 +44,7 @@ make_no_libnuma := NO_LIBNUMA=1
make_no_libaudit := NO_LIBAUDIT=1
make_no_libbionic := NO_LIBBIONIC=1
make_no_auxtrace := NO_AUXTRACE=1
+make_auxtrace := NO_AUXTRACE=0
make_tags := tags
make_cscope := cscope
make_help := help
@@ -94,6 +95,7 @@ run += make_no_libnuma
run += make_no_libaudit
run += make_no_libbionic
run += make_no_auxtrace
+run += make_auxtrace
run += make_help
run += make_doc
run += make_perf_o
--
1.9.1
next prev parent reply other threads:[~2015-08-25 10:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 10:42 [PATCH 1/2] perf tools: Fix build on powerpc broken by pt/bts Adrian Hunter
2015-08-25 10:42 ` Adrian Hunter [this message]
2015-08-25 15:30 ` Arnaldo Carvalho de Melo
2015-08-26 6:57 ` Adrian Hunter
2015-08-26 7:25 ` Jiri Olsa
2015-08-26 7:27 ` Adrian Hunter
2015-08-26 8:07 ` Jiri Olsa
2015-08-26 13:01 ` [PATCH] tools build: Allow duplicate objects in the object list Jiri Olsa
2015-08-28 6:41 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-08-26 13:08 ` [PATCH 1/2] perf tools: Fix build on powerpc broken by pt/bts Arnaldo Carvalho de Melo
2015-08-28 6:41 ` [tip:perf/core] perf tools: Remove export.h from MANIFEST tip-bot for Jiri Olsa
2015-08-26 7:06 ` [PATCH 1/2] perf tools: Fix build on powerpc broken by pt/bts Jiri Olsa
2015-08-31 18:39 ` [PATCH V2] " Adrian Hunter
2015-09-01 8:30 ` [tip:perf/urgent] perf tools: Fix build on powerpc broken by pt/ bts tip-bot for Adrian Hunter
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=1440499348-15629-2-git-send-email-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sukadev@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.