From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
Irina Tirdea <irina.tirdea@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
David Ahern <dsahern@gmail.com>,
Pekka Enberg <penberg@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Irina Tirdea <irina.tirdea@intel.com>
Subject: Re: [PATCH v2 3/4] perf annotate: configure objdump path at compile time
Date: Mon, 1 Oct 2012 07:27:37 -0700 [thread overview]
Message-ID: <20121001142737.GC9829@ghostprotocols.net> (raw)
In-Reply-To: <20121001072154.GA17143@gmail.com>
Em Mon, Oct 01, 2012 at 09:21:54AM +0200, Ingo Molnar escreveu:
> * Namhyung Kim <namhyung@kernel.org> wrote:
> > What I'm thinking is that perf can try to find cross-built binutils
> > when it detects perf.data file is came from other
> > machine/architecture. Fortunately perf_session_env was added
> > recently and it has the arch information from the file so we can use
> > it to find the path.
> > Following patch is a proof-of-concept patch and only build tested.
> > What do you think? Could you play with it for some time? :)
> This is a pretty clever idea - much better than hard-coding
> architecture details at build time.
Indeed, great idea!
- Arnaldo
next prev parent reply other threads:[~2012-10-01 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 19:27 [PATCH v2 0/4] perf: android: configure hardcoded paths Irina Tirdea
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 [this message]
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=20121001142737.GC9829@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=dsahern@gmail.com \
--cc=irina.tirdea@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