From: Irina Tirdea <irina.tirdea@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: LKML <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Pekka Enberg <penberg@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Irina Tirdea <irina.tirdea@intel.com>
Subject: [PATCH v2 0/4] perf: android: configure hardcoded paths
Date: Sun, 23 Sep 2012 22:27:22 +0300 [thread overview]
Message-ID: <1348428446-28245-1-git-send-email-irina.tirdea@gmail.com> (raw)
From: Irina Tirdea <irina.tirdea@intel.com>
This is version 2 of the set of patches that replace hardcoded paths used
in perf with configurable options in the Makefile.
First version can be found at https://lkml.org/lkml/2012/9/20/537.
Thanks everybody for the reviews! This version fixes all issues mentioned in
reviews.
Changes for v2:
() updated tools/perf/Documentation/jit-interface.txt regarding PERF_TMP_DIR
(patch 1)
() fixed hardcoded size for PERF_TMP_DIR"/perf-" (patch 1)
() use PERF_SHELL_PATH instead of PERF_SHELL_DIR (patch 2)
() use DEFAULT_OBJDUMP_PATH and DEFAULT_ADDR2LINE_PATH (patch 3,4)
() add CROSS_COMPILE prefix to addr2line and objdump in Makefile (patch 3,4)
Thanks,
Irina
Irina Tirdea (4):
perf tools: configure tmp path at build time
perf tools: configure shell path at compile time
perf annotate: configure objdump path at compile time
perf tools: configure addr2line path at compile time
tools/perf/Documentation/jit-interface.txt | 4 +++-
tools/perf/Makefile | 30 ++++++++++++++++++++++++++--
tools/perf/builtin-help.c | 2 +-
tools/perf/builtin-script.c | 12 +++++------
tools/perf/perf-archive.sh | 13 ++++++++++--
tools/perf/util/annotate.c | 5 +++--
tools/perf/util/dso-test-data.c | 2 +-
tools/perf/util/map.c | 3 ++-
tools/perf/util/pmu.c | 2 +-
tools/perf/util/sort.c | 2 +-
tools/perf/util/symbol.c | 4 +++-
tools/perf/util/trace-event-info.c | 2 +-
12 files changed, 61 insertions(+), 20 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-09-23 19:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 19:27 Irina Tirdea [this message]
2012-09-23 19:27 ` [PATCH v2 1/4] perf tools: configure tmp path at build time Irina Tirdea
2012-09-23 19:27 ` [PATCH v2 2/4] perf tools: configure shell path at compile time Irina Tirdea
2012-09-23 19:27 ` [PATCH v2 3/4] perf annotate: configure objdump " Irina Tirdea
2012-09-25 13:08 ` Namhyung Kim
2012-09-27 0:51 ` Irina Tirdea
2012-09-27 1:52 ` Namhyung Kim
2012-09-27 11:25 ` Irina Tirdea
2012-09-27 13:16 ` Namhyung Kim
2012-09-27 13:29 ` [RFC v2] perf tools: Try to find cross-built objdump path Namhyung Kim
2012-10-01 0:41 ` [RFC v3] " Irina Tirdea
2012-09-30 23:37 ` [PATCH v2 3/4] perf annotate: configure objdump path at compile time Irina Tirdea
2012-10-01 7:21 ` Ingo Molnar
2012-10-01 14:27 ` Arnaldo Carvalho de Melo
2012-09-23 19:27 ` [PATCH v2 4/4] perf tools: configure addr2line " Irina Tirdea
2012-09-23 19:49 ` [PATCH v3 " Irina Tirdea
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=1348428446-28245-1-git-send-email-irina.tirdea@gmail.com \
--to=irina.tirdea@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=irina.tirdea@intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=penberg@kernel.org \
--cc=rostedt@goodmis.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
Powered by JetHome