From: Hekuang <hekuang@huawei.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<alexander.shishkin@linux.intel.com>, <wangnan0@huawei.com>,
<jpoimboe@redhat.com>, <ak@linux.intel.com>, <eranian@google.com>,
<namhyung@kernel.org>, <adrian.hunter@intel.com>,
<sukadev@linux.vnet.ibm.com>, <masami.hiramatsu.pt@hitachi.com>,
<tumanova@linux.vnet.ibm.com>, <kan.liang@intel.com>,
<penberg@kernel.org>, <dsahern@gmail.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/6] perf tools: Promote proper messages for cross-platform unwind
Date: Fri, 20 May 2016 10:59:05 +0800 [thread overview]
Message-ID: <573E7D79.8080804@huawei.com> (raw)
In-Reply-To: <20160519164609.GC18909@krava>
hi
在 2016/5/20 0:46, Jiri Olsa 写道:
> On Thu, May 19, 2016 at 11:47:38AM +0000, He Kuang wrote:
>
> SNIP
>
>> #endif /* ARCH_PERF_COMMON_H */
>> diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile
>> index 1e46277..a86b864 100644
>> --- a/tools/perf/config/Makefile
>> +++ b/tools/perf/config/Makefile
>> @@ -345,6 +345,12 @@ ifeq ($(ARCH),powerpc)
>> endif
>>
>> ifndef NO_LIBUNWIND
>> + ifeq ($(feature-libunwind-x86), 1)
>> + LIBUNWIND_LIBS += -lunwind-x86
>> + $(call detected,CONFIG_LIBUNWIND_X86)
>> + CFLAGS += -DHAVE_LIBUNWIND_X86_SUPPORT
>> + endif
>> +
> how does one install that lirary?
>
> thanks,
> jirka
My work environment is on an old suse distribution, so it's
difficult to find libunwind-$arch rpm packages, so I build them
from source.
The git repository url is here:
http://git.savannah.gnu.org/r/libunwind.git(master)
Then flow the build step in README, first for i686:
$ ./autogen.sh
$ ./configure prefix=/xx/dst_i686 --target=i686-oe-linux
CC=x86_64-oe-linux-gcc
$ make && make install
Similar for aarch64:
$ make clean
$ ./configure prefix=/xx/dst_aarch64 --target=i686-oe-linux
CC=x86_64-oe-linux-gcc
$ make && make install
NOTICE: the contents in '--target' should be like
'i686-oe-linux', only give 'i686' cause strange build errors.
It looks like that libunwind don't support building for multiple
platforms at the same time, so I build them separately into
different directories.
Finally, copy the outputs into /usr/include and /usr/lib64, now
perf can detect them:
$ make VF=1 ARCH=x86_64 CROSS_COMPILE=x86_64-oe-linux-
EXTRA_CFLAGS="-m64"
...
... libunwind-x86: [ on ]
... libunwind-x86_64: [ OFF ]
... libunwind-arm: [ OFF ]
... libunwind-aarch64: [ on ]
Thanks.
next prev parent reply other threads:[~2016-05-20 3:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 11:47 [PATCH v4 0/6] Add support for remote unwind He Kuang
2016-05-19 11:47 ` [PATCH v4 1/6] perf tools: Set buildid dir under symfs when --symfs is provided He Kuang
2016-05-19 14:23 ` David Ahern
2016-05-19 16:07 ` Jiri Olsa
2016-05-20 17:46 ` [tip:perf/urgent] " tip-bot for He Kuang
2016-05-19 11:47 ` [PATCH v4 2/6] perf tools: Promote proper messages for cross-platform unwind He Kuang
2016-05-19 14:50 ` Arnaldo Carvalho de Melo
2016-05-19 16:19 ` Jiri Olsa
2016-05-20 3:00 ` Hekuang
2016-05-19 16:46 ` Jiri Olsa
2016-05-19 17:15 ` Jiri Olsa
2016-05-20 2:59 ` Hekuang [this message]
2016-05-20 9:53 ` Jiri Olsa
2016-05-19 11:47 ` [PATCH v4 3/6] perf tools: Separate local and remote unwind support detection He Kuang
2016-05-19 11:47 ` [PATCH v4 4/6] perf callchain: Add support for cross-platform unwind He Kuang
2016-05-19 11:47 ` [PATCH v4 5/6] perf callchain: Support x86 target platform He Kuang
2016-05-19 11:47 ` [PATCH v4 6/6] perf callchain: Support aarch64 cross-platform He Kuang
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=573E7D79.8080804@huawei.com \
--to=hekuang@huawei.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=sukadev@linux.vnet.ibm.com \
--cc=tumanova@linux.vnet.ibm.com \
--cc=wangnan0@huawei.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.