From: "H. Peter Anvin" <hpa@zytor.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Paul Mackerras <paulus@samba.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: BUG: different symbol address between System.map and /proc/kallsyms
Date: Sun, 20 Dec 2009 22:31:12 -0800 [thread overview]
Message-ID: <4B2F1630.7090406@zytor.com> (raw)
In-Reply-To: <4B2ECD47.7040202@cn.fujitsu.com>
On 12/20/2009 05:20 PM, Xiao Guangrong wrote:
> Hi,
>
> The symbol address in System.map and /proc/kallsys is different:
>
> # cat System.map | grep _text
> c1000000 T _text
> # cat /proc/kallsyms | grep _text
> c0100000 T _text
>
> # readelf -s vmlinux | grep _text
> 35078: c1000000 0 NOTYPE GLOBAL DEFAULT 1 _text
>
> So, perf can't get sysmbol address properly:
>
> # ./perf report
> # Samples: 29
> #
> # Overhead Command Shared Object Symbol
> # ........ ....... ................... ......
> #
> 93.10% sleep c014f988 [k] 0x000000c014f988
> 3.45% sleep libc-2.9.90.so [.] _int_malloc
> 3.45% sleep [kernel] [k] 0x000000c014f988
That is normal if you have a relocatable kernel which has been loaded at
the non-compile-time default address.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-12-21 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 1:20 BUG: different symbol address between System.map and /proc/kallsyms Xiao Guangrong
2009-12-21 1:23 ` Xiao Guangrong
2009-12-21 6:31 ` H. Peter Anvin [this message]
2009-12-21 9:13 ` Xiao Guangrong
2009-12-21 9:34 ` Ingo Molnar
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=4B2F1630.7090406@zytor.com \
--to=hpa@zytor.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=xiaoguangrong@cn.fujitsu.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.