From: "" <pmarques@grupopie.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: "" <linux-kernel@vger.kernel.org>
Subject: Re: sh: inconsistent kallsyms data
Date: Fri, 31 Dec 2004 19:29:16 +0000 [thread overview]
Message-ID: <1104521356.41d5a88c041ff@webmail.grupopie.com> (raw)
In-Reply-To: <20041231182234.GB18211@linux-sh.org>
Quoting Paul Mundt <lethal@linux-sh.org>:
> On Fri, Dec 31, 2004 at 05:59:31PM +0000, pmarques@grupopie.com wrote:
> > I think the only change from 2.6.9 that could affect this is the
> > addition of the is_arm_mapping_symbol from Russel King.
> >
> This wouldn't make any difference as that only gets invoked by
> read_symbol() for U type symbols, which is unrelated.
You mis-read the 'if'. The symbol is not used it is of 'U' type *or*
is_arm_mapping_symbol. This means that is_arm_mapping_symbol will be called for
all the symbols that are not of type 'U'.
Anyway, Keith Owens might be right. I forgot that this change only went into the
official tree now, and was under the impression that was already in 2.6.9 :(
It seems from the symptoms that the kallsyms_names array was 0x70 bytes larger
on the second run. This shouldn't happen if the algorithm is ran over the same
symbols, not matter how complex the algorithm is.
I was the one who wrote the algorithm, so I'm probably in the best position to
debug it. If you send Keith the info he requested, send it to me too, so that I
have some more data to look at.
--
Paulo Marques - www.grupopie.com
"A journey of a thousand miles begins with a single step."
Lao-tzu, The Way of Lao-tzu
next prev parent reply other threads:[~2004-12-31 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-31 17:25 Paul Mundt
2004-12-31 17:59 ` pmarques
2004-12-31 18:22 ` Paul Mundt
2004-12-31 19:29 ` pmarques [this message]
2004-12-31 19:42 ` Paul Mundt
2004-12-31 18:15 ` Keith Owens
2005-01-01 3:59 ` Keith Owens
2005-01-01 4:15 ` Keith Owens
2005-01-01 9:01 ` Paul Mundt
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=1104521356.41d5a88c041ff@webmail.grupopie.com \
--to=pmarques@grupopie.com \
--cc=lethal@linux-sh.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
Powered by JetHome