From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] scripts/kallsyms: filter symbols not in kernel address space
Date: Tue, 07 Jan 2014 16:05:43 +0100 [thread overview]
Message-ID: <5082388.oRuzc7DqM3@wuerfel> (raw)
In-Reply-To: <CACVXFVNPcC+7Th-xfD24GiEat=FHMGKXh9Abc_othvR5pdLOYQ@mail.gmail.com>
On Tuesday 07 January 2014 22:33:24 Ming Lei wrote:
> On Tue, Jan 7, 2014 at 10:12 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Monday 28 October 2013, Ming Lei wrote:
>
> We had posted two patches to address the problem, see below link:
>
> http://lists.scusting.com/index.php?t=msg&goto=1726509&S=Google
The patch "scripts/link-vmlinux.sh: only filter kernel symbols for arm"
has made it in now, which is good for all other architectures, but it
makes no difference for nommu-arm, because CONFIG_PAGE_OFFSET is
still set.
The second patch from Jonathan Austin has not been applied yet, as of
today's linux-next, and it's exactly what I suggested. However it
won't work on ARM platforms that define their own PLAT_PHYS_OFFSET:
ebsa110, ep93xx, exynos, footbridge, integrator, iop13xx, ks8695,
omap1, realview, rpc, s5pv210 and sa1100. Fortunately these all have
MMUs, so in practice it won't hurt, but it doesn't seem correct.
Arnd
prev parent reply other threads:[~2014-01-07 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 15:48 [PATCH] scripts/kallsyms: filter symbols not in kernel address space Ming Lei
2013-10-31 22:43 ` Andrew Morton
2013-10-31 22:50 ` Russell King - ARM Linux
2013-10-31 22:58 ` Andrew Morton
2013-10-31 23:53 ` Russell King - ARM Linux
2013-11-01 2:10 ` Ming Lei
2013-11-01 2:36 ` Rusty Russell
2013-11-01 4:38 ` Stephen Rothwell
2014-01-07 14:12 ` Arnd Bergmann
2014-01-07 14:33 ` Ming Lei
2014-01-07 15:05 ` Arnd Bergmann [this message]
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=5082388.oRuzc7DqM3@wuerfel \
--to=arnd@arndb.de \
--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