All of lore.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, davem@davemloft.net,
	anil.s.keshavamurthy@intel.com, ananth@in.ibm.com,
	radovan.lekanovic@sonymobile.com, bjorn.davidsson@sonymobile.com,
	"yrl.pp-manager.tt@hitachi.com" <yrl.pp-manager.tt@hitachi.com>
Subject: Re: [PATCH 2/4] kprobes: split blacklist into common and arch
Date: Thu, 04 Apr 2013 15:17:25 +0900	[thread overview]
Message-ID: <515D1AF5.3010900@hitachi.com> (raw)
In-Reply-To: <1364977734-32267-3-git-send-email-oskar.andero@sonymobile.com>

(2013/04/03 17:28), oskar.andero@sonymobile.com wrote:
> Some blackpoints are only valid for specific architectures. To let each
> architecture specify its own blackpoints the list has been split in two
> lists: common and arch. The common list is kept in kernel/kprobes.c and
> the arch list is kept in the arch/ directory.

Hmm, I think you'd better merge this with patch 3/4.

[...]
> +static const size_t common_kprobes_blacksyms_size =
> +			ARRAY_SIZE(common_kprobes_blacksyms);
> +
> +extern const char * const arch_kprobes_blacksyms[];
> +extern const size_t arch_kprobes_blacksyms_size;
> +
> +static struct kprobe_blackpoint **kprobe_blacklist;
> +static size_t kprobe_blacklist_size;

Since the blacklist is allocated once and never be updated,
we just need an array of struct kprobe_blackpoint, no need
to allocate each entry.

Other parts are good for me! :)

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-04-04  6:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  8:28 [PATCH 0/4] kprobes: split blacklist into common and arch oskar.andero
2013-04-03  8:28 ` [PATCH 1/4] kprobes: delay blacklist symbol lookup until we actually need it oskar.andero
2013-04-04  6:44   ` Masami Hiramatsu
2013-04-04  7:57     ` Oskar Andero
2013-04-03  8:28 ` [PATCH 2/4] kprobes: split blacklist into common and arch oskar.andero
2013-04-04  6:17   ` Masami Hiramatsu [this message]
2013-04-04 11:49     ` Oskar Andero
2013-04-03  8:28 ` [PATCH 3/4] kprobes: move x86-specific blacklist symbols to arch directory oskar.andero
2013-04-03  8:28 ` [PATCH 4/4] kprobes: replace printk with pr_-functions oskar.andero
2013-04-04  6:19   ` Masami Hiramatsu
2013-04-04 11:32 ` [PATCH 0/4] kprobes: split blacklist into common and arch Vineet Gupta
2013-04-04 11:32   ` Vineet Gupta
2013-04-04 11:41   ` Oskar Andero

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=515D1AF5.3010900@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.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=oskar.andero@sonymobile.com \
    --cc=radovan.lekanovic@sonymobile.com \
    --cc=yrl.pp-manager.tt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.