From: Namhyung Kim <namhyung@kernel.org>
To: Jean Pihet <jean.pihet@linaro.org>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
".Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: perf: cannot resolve kernel symbols
Date: Mon, 23 Sep 2013 15:58:31 +0900 [thread overview]
Message-ID: <87d2o0qb1k.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <CAFrcx1mL4ozbprh5hAb9usopDReZNbbk6jcMS=f=SGG7N2_BUw@mail.gmail.com> (Jean Pihet's message of "Thu, 19 Sep 2013 15:24:56 +0200")
Hi Jean,
On Thu, 19 Sep 2013 15:24:56 +0200, Jean Pihet wrote:
> Hi,
>
> Ping on this issue. Any idea or pointer.
Did you build perf without libelf?
Thanks,
Namhyung
>
> Cheers,
> Jean
>
> On 17 September 2013 14:02, Jean Pihet <jean.pihet@linaro.org> wrote:
>> Hi,
>>
>> I am running the perf record and report commands, which are running OK
>> but I do not get any kernel symbol resolved when using a built and
>> installed kernel.
>> Using the distro installed kernel is OK though.
>> The setup is: Marvell ARMv7 quad core, Linaro Ubuntu release.
>>
>> Here are the commands in use:
>> - perf record -g dwarf -- stress --cpu 2 --io 2 --vm 2 --timeout 1s
>> - perf report -vvv
>>
>> With a vmlinux found at /lib/modules/<version>/build I get the
>> following in the trace output:
>> ...
>> Looking at the vmlinux_path (6 entries long)
>> Using /lib/modules/3.11.0-00003-g0d4d4a1/build/vmlinux for symbols
>> ...
>> dso: [kernel.kallsyms]
>> (/lib/modules/3.11.0-00003-g0d4d4a1/build/vmlinux, Functions, loaded,
>> 0000000000000000000000000000000000000000)
>> c00081c0-c00081c3 g asm_do_IRQ
>> ...
>> dso: [kernel.kallsyms].head.text ([kernel.kallsyms], Functions, loaded, 00000000
>> 00000000000000000000000000000000)
>> c0008000-c0008077 g stext
>> c0008000-c0008000 g _text
>> c0008084-c0008127 l __create_page_tables
>> ...
>> dso: [kernel.kallsyms].init.text ([kernel.kallsyms], Functions, loaded, 00000000
>> 00000000000000000000000000000000)
>> c04f3260-c04f32af l __fixup_smp
>>
>>
>> Without any vmlinux found I get the following:
>> ...
>> Looking at the vmlinux_path (6 entries long)
>> Using /proc/kallsyms for symbols
>> ...
>> dso: [kernel.kallsyms] ([kernel.kallsyms], Functions, loaded,
>> 0000000000000000000000000000000000000000)
>> 0-beffffff l __vectors_start
>> dso: [kernel.kallsyms] ([kernel.kallsyms], Variables, NOT loaded,
>> 0000000000000000000000000000000000000000)
>> dso: stress (/usr/bin/stress, Functions, loaded,
>> bdf57306ab106fb0ce9835c95dae5b173f238b61)
>> ...
>>
>>
>> In any case the symbols are not resolved although vmlinux contains
>> symbols and /proc/kallsyms is accessible and working correctly.
>> Any idea on where to look at? I guess the problem is in the kernel installation.
>>
>> Thx & regards,
>> Jean
next prev parent reply other threads:[~2013-09-23 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 12:02 Jean Pihet
2013-09-19 13:24 ` Jean Pihet
2013-09-23 6:58 ` Namhyung Kim [this message]
2013-09-23 7:43 ` Jean Pihet
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=87d2o0qb1k.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=jean.pihet@linaro.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®