From: Paulo Marques <pmarques@grupopie.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: /proc/kallsyms broken in 2.6.26-rc1-git6
Date: Mon, 12 May 2008 11:00:32 +0100 [thread overview]
Message-ID: <48281540.9020207@grupopie.com> (raw)
In-Reply-To: <20080509233742.GA22265@martell.zuzino.mipt.ru>
Alexey Dobriyan wrote:
> On Fri, May 09, 2008 at 08:59:56PM +0100, Paulo Marques wrote:
>> Andi Kleen wrote:
>>>[...]
>>> Yes and? Surely that's not correct?
>> That's not for me to judge, but I believe it has always been like that.
>
> *cough*
>
> Here is how typical /proc/kallsyms looks like:
>
> ffffffff80200000 A _text
> ffffffff80200000 T startup_64
> ffffffff802000b7 t ident_complete
> ffffffff80200100 T secondary_startup_64
This isn't helpful... the question is whether it is kallsyms misbehaving
and placing new symbols in the kernel image or if it is some other
change in the kernel that is generating new symbols that end up in the
symbol table.
My guess it is that it is the later, and in that case, from a kallsyms
standpoint "it has always been like that".
--
Paulo Marques - www.grupopie.com
"God is love. Love is blind. Ray Charles is blind. Ray Charles is God."
next prev parent reply other threads:[~2008-05-12 10:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 17:41 /proc/kallsyms broken in 2.6.26-rc1-git6 Andi Kleen
2008-05-09 18:03 ` Paulo Marques
2008-05-09 19:36 ` Andi Kleen
2008-05-09 19:59 ` Paulo Marques
2008-05-09 23:16 ` Andi Kleen
2008-05-12 9:55 ` Paulo Marques
2008-05-12 10:08 ` Andi Kleen
2008-05-09 23:37 ` Alexey Dobriyan
2008-05-12 10:00 ` Paulo Marques [this message]
2008-05-12 15:50 ` Cyrill Gorcunov
2008-05-12 17:23 ` Sam Ravnborg
2008-05-12 17:28 ` Cyrill Gorcunov
2008-05-13 9:54 ` Andi Kleen
2008-05-19 18:11 ` Sam Ravnborg
2008-05-19 18:15 ` Cyrill Gorcunov
2008-05-19 18:21 ` Sam Ravnborg
2008-05-19 18:22 ` Cyrill Gorcunov
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=48281540.9020207@grupopie.com \
--to=pmarques@grupopie.com \
--cc=adobriyan@gmail.com \
--cc=andi@firstfloor.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