From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jim Keniston <jkenisto@us.ibm.com>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
systemtap-ml <systemtap@sources.redhat.com>,
Maneesh Soni <maneesh@linux.vnet.ibm.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Subject: Re: [RFC][PATCH -mm 0/6] kprobes: Per-probe disabling support
Date: Tue, 13 Jan 2009 10:38:31 +0530 [thread overview]
Message-ID: <20090113050831.GF12392@in.ibm.com> (raw)
In-Reply-To: <496BF48F.2030300@redhat.com>
On Mon, Jan 12, 2009 at 08:55:27PM -0500, Masami Hiramatsu wrote:
> Hi,
>
> Currently, kprobes can disable all probes at once, but can't disable it
> individually (not unregister, just disable an kprobe, because unregistering
> needs to wait for scheduler synchronization).
> These patches introduce APIs for on-the-fly per-probe disabling and
> re-enabling by dis-arming/re-arming its breakpoint instruction.
>
> These patches can be applied on the latest -mm tree including my previous
> bugfix patch (http://lkml.org/lkml/2009/1/5/472).
>
> You can download a test of this feature from here:
> http://sources.redhat.com/bugzilla/attachment.cgi?id=3082&action=view
>
> Thank you,
>
> Documentation/kprobes.txt | 38 +++++-
> include/linux/kprobes.h | 51 +++++++-
> kernel/kprobes.c | 281 ++++++++++++++++++++++++++++++++--------------
> 3 files changed, 279 insertions(+), 91 deletions(-)
Acked-by: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
...for the patchset.
Thanks for the work Masami. We'll need to allow this set to cook in
-mm/next for a few weeks before it goes upstream.
Ananth
prev parent reply other threads:[~2009-01-13 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 1:55 [RFC][PATCH -mm 0/6] kprobes: Per-probe disabling support Masami Hiramatsu
2009-01-13 5:08 ` Ananth N Mavinakayanahalli [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=20090113050831.GF12392@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@linux.vnet.ibm.com \
--cc=mhiramat@redhat.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=systemtap@sources.redhat.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.