[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <513967BD.9010602@hitachi.com>
Date: Fri, 08 Mar 2013 13:23:25 +0900
From: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
To: oskar.andero@...ymobile.com
Cc: linux-kernel@...r.kernel.org, davem@...emloft.net,
anil.s.keshavamurthy@...el.com, ananth@...ibm.com,
radovan.lekanovic@...ymobile.com,
� <bjorn.davidsson@...ymobile.com>
Subject: Re: [PATCH] Kprobes blacklist: Conditionally add x86-specific
symbols
(2013/03/07 19:44), oskar.andero@...ymobile.com wrote:
> From: Bjorn Davidsson <bjorn.davidsson@...ymobile.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...
Would you know some other black points on your platform?
Thank you,
>
> Reviewed-by: Radovan Lekanovic <radovan.lekanovic@...ymobile.com>
> Signed-off-by: Björn Davidsson <bjorn.davidsson@...ymobile.com>
> Signed-off-by: Oskar Andero <oskar.andero@...ymobile.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@...achi.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists