From: <oskar.andero@sonymobile.com>
To: <linux-kernel@vger.kernel.org>
Cc: masami.hiramatsu.pt@hitachi.com, davem@davemloft.net,
anil.s.keshavamurthy@intel.com, ananth@in.ibm.com,
radovan.lekanovic@sonymobile.com,
"Bj�rn Davidsson" <bjorn.davidsson@sonymobile.com>,
"Oskar Andero" <oskar.andero@sonymobile.com>
Subject: [PATCH] Kprobes blacklist: Conditionally add x86-specific symbols
Date: Thu, 7 Mar 2013 11:44:30 +0100 [thread overview]
Message-ID: <1362653070-24035-1-git-send-email-oskar.andero@sonymobile.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 1016 bytes --]
From: Björn Davidsson <bjorn.davidsson@sonymobile.com>
The kprobes blacklist contains x86-specific symbols.
Looking for these in kallsyms takes unnecessary time
during startup on non-X86 platform.
Added #ifdef CONFIG_X86 around them.
Reviewed-by: Radovan Lekanovic <radovan.lekanovic@sonymobile.com>
Signed-off-by: Björn Davidsson <bjorn.davidsson@sonymobile.com>
Signed-off-by: Oskar Andero <oskar.andero@sonymobile.com>
---
kernel/kprobes.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/kernel/kprobes.c b/kernel/kprobes.c
index e35be53..8c3796f 100644
--- a/kernel/kprobes.c
+++ b/kernel/kprobes.c
@@ -95,9 +95,11 @@ static raw_spinlock_t *kretprobe_table_lock_ptr(unsigned long hash)
*/
static struct kprobe_blackpoint kprobe_blacklist[] = {
{"preempt_schedule",},
+#ifdef CONFIG_X86
{"native_get_debugreg",},
{"irq_entries_start",},
{"common_interrupt",},
+#endif
{"mcount",}, /* mcount can be called from everywhere */
{NULL} /* Terminator */
};
--
1.7.8.6
next reply other threads:[~2013-03-07 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 10:44 oskar.andero [this message]
2013-03-08 4:23 ` Masami Hiramatsu
2013-03-08 6:03 ` Ananth N Mavinakayanahalli
2013-03-08 13:17 ` oskar.andero
2013-03-08 13:15 ` oskar.andero
2013-03-09 1:23 ` Masami Hiramatsu
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=1362653070-24035-1-git-send-email-oskar.andero@sonymobile.com \
--to=oskar.andero@sonymobile.com \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bjorn.davidsson@sonymobile.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=radovan.lekanovic@sonymobile.com \
/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
all inboxes | Powered by JetHome®