From: akpm@linux-foundation.org (Andrew Morton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] scripts/kallsyms: filter symbols not in kernel address space
Date: Thu, 31 Oct 2013 15:43:11 -0700 [thread overview]
Message-ID: <20131031154311.e65d16d79ba540ced736413b@linux-foundation.org> (raw)
In-Reply-To: <1382975339-25831-1-git-send-email-tom.leiming@gmail.com>
On Mon, 28 Oct 2013 23:48:59 +0800 Ming Lei <tom.leiming@gmail.com> wrote:
> This patch uses CONFIG_PAGE_OFFSET to filter symbols which
> are not in kernel address space because these symbols are
> generally for generating code purpose and can't be run at
> kernel mode, so we needn't keep them in /proc/kallsyms.
>
> For example, on ARM there are some symbols which are
> linked in relocatable code section, then perf can't parse
> symbols any more from /proc/kallsyms, and this patch fixes
> the problem.
This is a non-back-compatible change and I'd like to see a much
stronger assurance that it is safe to merge and will not break any
existing application on the planet, please.
For a start, please describe with great precision what these excluded
symbols are (examples would help) and explain why no application will
conceivably have had any use for them.
next prev parent reply other threads:[~2013-10-31 22:43 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 [this message]
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
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=20131031154311.e65d16d79ba540ced736413b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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).