From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Inconsistent kallsyms data on ARM.
Date: Mon, 26 Mar 2012 08:37:04 +0100 [thread overview]
Message-ID: <20120326073704.GH5611@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4F6FB170.1040109@jonmasters.org>
On Sun, Mar 25, 2012 at 07:59:44PM -0400, Jon Masters wrote:
> As to longer term, I am happy to work up something that will spot this
> particular kind of failure (symbol changes type) and output something
> more useful during the kallsyms generation if you would like.
>
> Are you planning to pull in either of the fixes you mention?
I'm not, because those are all sub-optimal - I don't see why we should
bloat the kernel image just for the sake of working around kallsyms.
The best I've come up with so far which avoids that is to force
KALLSYMS_EXTRA_PASS to always be set on ARM.
next prev parent reply other threads:[~2012-03-26 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 22:00 Inconsistent kallsyms data on ARM Paul Gortmaker
2012-03-14 13:21 ` Arnd Bergmann
2012-03-25 11:20 ` Russell King - ARM Linux
2012-03-25 23:59 ` Jon Masters
2012-03-26 7:37 ` Russell King - ARM Linux [this message]
2012-03-26 7:45 ` Uwe Kleine-König
2012-03-26 8:39 ` Arnd Bergmann
2012-03-26 13:07 ` Jon Masters
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=20120326073704.GH5611@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).