From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: mingo@elte.hu, Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Roland McGrath <roland@redhat.com>
Subject: Re: [Patch 11/11] ftrace plugin for kernel symbol tracing using HW Breakpoint interfaces - v2
Date: Sat, 7 Mar 2009 23:51:06 +0530 [thread overview]
Message-ID: <20090307182106.GA7524@in.ibm.com> (raw)
In-Reply-To: <20090307222955.25A7.A69D9226@jp.fujitsu.com>
On Sat, Mar 07, 2009 at 11:53:46PM +0900, KOSAKI Motohiro wrote:
> Hi
>
> > This patch adds an ftrace plugin to detect and profile memory access over
> > kernel variables. It uses HW Breakpoint interfaces to 'watch memory
> > addresses.
> >
> > Signed-off-by: K.Prasad <prasad@linux.vnet.ibm.com>
> > ---
> > kernel/trace/Kconfig | 6
> > kernel/trace/Makefile | 1
> > kernel/trace/trace.h | 16 +
> > kernel/trace/trace_ksym.c | 448 ++++++++++++++++++++++++++++++++++++++++++
> > kernel/trace/trace_selftest.c | 36 +++
> > 5 files changed, 507 insertions(+)
>
> Could you please update Documentation/ftrace.txt?
> I guess many user interesting this patch. :)
>
Sure. We have plans for a documentation file for the hardware breakpoint
interfaces (something like Documentation/hw_breakpoint.txt). I shall
update the Documentation/ftrace.txt with usage details for the kernel
symbol tracing plugin along with them.
Thanks,
K.Prasad
next prev parent reply other threads:[~2009-03-07 18:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090307045120.039324630@linux.vnet.ibm.com>
2009-03-07 5:04 ` [Patch 01/11] Introducing generic hardware breakpoint handler interfaces prasad
2009-03-07 5:05 ` [Patch 02/11] x86 architecture implementation of Hardware Breakpoint interfaces prasad
2009-03-07 5:06 ` [Patch 03/11] Modifying generic debug exception to use virtual debug registers prasad
2009-03-07 5:06 ` [Patch 04/11] Introduce virtual debug register in thread_struct and wrapper-routines around process related functions prasad
2009-03-07 5:06 ` [Patch 05/11] Use wrapper routines around debug registers in processor " prasad
2009-03-07 5:06 ` [Patch 06/11] Use virtual debug registers in process/thread handling code prasad
2009-03-07 5:06 ` [Patch 07/11] Modify signal handling code to refrain from re-enabling HW Breakpoints prasad
2009-03-07 5:07 ` [Patch 08/11] Modify Ptrace routines to access breakpoint registers prasad
2009-03-07 5:07 ` [Patch 09/11] Cleanup HW Breakpoint registers before kexec prasad
2009-03-07 5:07 ` [Patch 10/11] Sample HW breakpoint over kernel data address prasad
2009-03-07 5:07 ` [Patch 11/11] ftrace plugin for kernel symbol tracing using HW Breakpoint interfaces - v2 prasad
2009-03-07 14:53 ` KOSAKI Motohiro
2009-03-07 18:21 ` K.Prasad [this message]
2009-03-08 10:09 ` Ingo Molnar
2009-03-08 11:00 ` Frederic Weisbecker
2009-03-10 12:21 ` K.Prasad
2009-03-10 19:55 ` Frederic Weisbecker
2009-03-09 21:36 ` K.Prasad
[not found] <20090319234044.410725944@K.Prasad>
2009-03-19 23:50 ` K.Prasad
2009-03-20 9:04 ` Frederic Weisbecker
2009-03-21 16:24 ` K.Prasad
2009-03-21 16:39 ` Steven Rostedt
2009-03-23 19:08 ` K.Prasad
[not found] <20090324152028.754123712@K.Prasad>
2009-03-24 15:28 ` K.Prasad
2009-03-22 9:35 ` Pavel Machek
2009-03-25 3:03 ` Steven Rostedt
2009-03-25 3:30 ` K.Prasad
2009-03-25 3:48 ` Steven Rostedt
[not found] <20090407063058.301701787@prasadkr_t60p.in.ibm.com>
2009-04-07 6:37 ` K.Prasad
2009-04-08 8:02 ` Frederic Weisbecker
2009-04-08 11:12 ` K.Prasad
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=20090307182106.GA7524@in.ibm.com \
--to=prasad@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=stern@rowland.harvard.edu \
/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.