public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: oskar.andero@sonymobile.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: Re: [PATCH] Kprobes blacklist: Conditionally add x86-specific symbols
Date: Sat, 09 Mar 2013 10:23:31 +0900	[thread overview]
Message-ID: <513A8F13.3070402@hitachi.com> (raw)
In-Reply-To: <20130308131534.GI26148@caracas.corpusers.net>

(2013/03/08 22:15), oskar.andero@sonymobile.com wrote:
> 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.

Yes, we can have symbol tables (const char *arch_kprobes_blacksyms[],
common_kprobes_blacksyms[]) to list it up, and when initializing
the blacklist table, we can check whether kprobes_blacklist == NULL
and initialize it.

Thank you,

-- 
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com



      reply	other threads:[~2013-03-09  1:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 10:44 [PATCH] Kprobes blacklist: Conditionally add x86-specific symbols 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
2013-03-09  1:23     ` Masami Hiramatsu [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=513A8F13.3070402@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.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=oskar.andero@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