Re: [PATCH v2 3/4] perf annotate: configure objdump path at compile time

2012-10-01 Thread Arnaldo Carvalho de Melo
Em Mon, Oct 01, 2012 at 09:21:54AM +0200, Ingo Molnar escreveu: > * Namhyung Kim 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

Re: [PATCH v2 3/4] perf annotate: configure objdump path at compile time

2012-10-01 Thread Ingo Molnar
* Namhyung Kim wrote: > On Thu, 27 Sep 2012 14:25:10 +0300, Irina Tirdea wrote: > >>> The perf built to run on the host needs to use arm-eabi-objdump from > >>> the toolchain so that it can analyse data recorded on Android. This > >>> patch is targeting this scenario, not the previous one. In th

Re: [PATCH v2 3/4] perf annotate: configure objdump path at compile time

2012-09-30 Thread Irina Tirdea
On Thu, Sep 27, 2012 at 4:16 PM, Namhyung Kim wrote: > On Thu, 27 Sep 2012 14:25:10 +0300, Irina Tirdea wrote: The perf built to run on the host needs to use arm-eabi-objdump from the toolchain so that it can analyse data recorded on Android. This patch is targeting this scenario, n

Re: [PATCH v2 3/4] perf annotate: configure objdump path at compile time

2012-09-27 Thread Namhyung Kim
On Thu, 27 Sep 2012 14:25:10 +0300, Irina Tirdea wrote: >>> The perf built to run on the host needs to use arm-eabi-objdump from >>> the toolchain so that it can analyse data recorded on Android. This >>> patch is targeting this scenario, not the previous one. In this case, >>> the CROSS_COMPILE op

Re: [PATCH v2 3/4] perf annotate: configure objdump path at compile time

2012-09-27 Thread Irina Tirdea
>> The perf built to run on the host needs to use arm-eabi-objdump from >> the toolchain so that it can analyse data recorded on Android. This >> patch is targeting this scenario, not the previous one. In this case, >> the CROSS_COMPILE option would be different than arm-eabi- so using >> $(CROSS_C

Re: [PATCH v2 3/4] perf annotate: configure objdump path at compile time

2012-09-26 Thread Namhyung Kim
On Thu, 27 Sep 2012 03:51:07 +0300, Irina Tirdea wrote: > On Tue, Sep 25, 2012 at 4:08 PM, Namhyung Kim wrote: >> I thought about it twice and confused. >> >> For cross-compiling, the resulting perf binary will run on target - say >> Android - but the toolchain runs on host, right? So with this c

Re: [PATCH v2 3/4] perf annotate: configure objdump path at compile time

2012-09-26 Thread Irina Tirdea
On Tue, Sep 25, 2012 at 4:08 PM, Namhyung Kim wrote: > Hi Irina, Hi Namhyung, > 2012-09-23 (일), 22:27 +0300, Irina Tirdea: >> From: Irina Tirdea >> >> The default name for objdump is "objdump". For cross-compiling the name of >> objdump will be different (e.g. arm-eabi-objdump in Android). >> >

Re: [PATCH v2 3/4] perf annotate: configure objdump path at compile time

2012-09-25 Thread Namhyung Kim
Hi Irina, 2012-09-23 (일), 22:27 +0300, Irina Tirdea: > From: Irina Tirdea > > The default name for objdump is "objdump". For cross-compiling the name of > objdump will be different (e.g. arm-eabi-objdump in Android). > > Set the default objdump name in the Makefile with DEFAULT_OBJDUMP_PATH. I

[PATCH v2 3/4] perf annotate: configure objdump path at compile time

2012-09-23 Thread Irina Tirdea
From: Irina Tirdea The default name for objdump is "objdump". For cross-compiling the name of objdump will be different (e.g. arm-eabi-objdump in Android). Set the default objdump name in the Makefile with DEFAULT_OBJDUMP_PATH. Signed-off-by: Irina Tirdea --- tools/perf/Makefile|4