public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Ingo Molnar <mingo@redhat.com>
Cc: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>,
		Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
		"bibo,mao" <bibo.mao@intel.com>,
		Prasanna S Panchamukhi <prasanna@in.ibm.com>,
		Andrew Morton <akpm@osdl.org>,
		linux-kernel <linux-kernel@vger.kernel.org>,
		SystemTAP <systemtap@sources.redhat.com>,
		Yumiko Sugita <yumiko.sugita.yf@hitachi.com>,
		Satoshi Oshima <soshima@redhat.com>,
	Hideo Aoki <haoki@redhat.com>
Subject: Re: [PATCH][kprobe] enabling booster on the preemptible kernel
Date: Tue, 21 Nov 2006 00:45:00 -0000	[thread overview]
Message-ID: <45624BF2.8040906@hitachi.com> (raw)
In-Reply-To: <1163775843.8789.55.camel@earth>

Hi Ingo,

Ingo Molnar wrote:
> On Fri, 2006-11-17 at 21:35 +0900, Masami Hiramatsu wrote:
>> From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
>>
>> This patch enables the kprobe-booster on the preemptible kernel.
>> For this purpose, I introduced a kind of garbage collector of
>> the instruction slots. This garbage collector checks safety before
>> releasing the garbage slots.
>>
>> Signed-off-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> 
> 
> nice work - looks really sensible! This opens the door to djprobes (or
> rather, to the transparent kprobes speedup that used to be a separate
> interface), right?

Right. Actually, I already integrated djprobe and kprobes.
I'll post it as soon as possible.

> 
>  Acked-by: Ingo Molnar <mingo@elte.hu>

Thank you.

-- 
Masami HIRAMATSU
Linux Technology Center
Hitachi, Ltd., Systems Development Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com


      reply	other threads:[~2006-11-21  0:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 13:54 Masami Hiramatsu
2006-11-17 15:05 ` Keshavamurthy, Anil S
2006-11-17 15:40 ` Ingo Molnar
2006-11-21  0:45   ` 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=45624BF2.8040906@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=akpm@osdl.org \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=bibo.mao@intel.com \
    --cc=haoki@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=prasanna@in.ibm.com \
    --cc=soshima@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --cc=yumiko.sugita.yf@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).