From: <oskar.andero@sonymobile.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"anil.s.keshavamurthy@intel.com" <anil.s.keshavamurthy@intel.com>,
"ananth@in.ibm.com" <ananth@in.ibm.com>,
"Lekanovic, Radovan" <Radovan.Lekanovic@sonymobile.com>,
"Davidsson, Björn" <Bjorn.Davidsson@sonymobile.com>
Subject: Re: [PATCH] Kprobes blacklist: Conditionally add x86-specific symbols
Date: Fri, 8 Mar 2013 14:15:35 +0100 [thread overview]
Message-ID: <20130308131534.GI26148@caracas.corpusers.net> (raw)
In-Reply-To: <513967BD.9010602@hitachi.com>
On 05:23 Fri 08 Mar , Masami Hiramatsu wrote:
> (2013/03/07 19:44), oskar.andero@sonymobile.com wrote:
> > From: Bjorn 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.
>
> Right. however, it might be better break that into
> common and arch-specific lists, because there may be
> other arch-specific non-probe-able functions on each
> architecture...
Ok. You mean adding, for instance, a kprobe_blacklist_arch[] in arch/x86
somewhere or did you have something else in mind? I guess we preferably want
to get rid of the #ifdef.
> Would you know some other black points on your platform?
Not that we are aware of.
> Thank you,
>
> >
> > 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 */
> > };
> >
>
>
> --
> Masami HIRAMATSU
> IT Management Research Dept. Linux Technology Center
> Hitachi, Ltd., Yokohama Research Laboratory
> E-mail: masami.hiramatsu.pt@hitachi.com
>
>
-Oskar
next prev parent reply other threads:[~2013-03-08 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 10:44 oskar.andero
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 [this message]
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=20130308131534.GI26148@caracas.corpusers.net \
--to=oskar.andero@sonymobile.com \
--cc=Bjorn.Davidsson@sonymobile.com \
--cc=Radovan.Lekanovic@sonymobile.com \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.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®