From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Cc: Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>
Subject: [PATCH -tip 0/4] perf-probe updates: string support, etc.
Date: Wed, 19 May 2010 15:57:17 -0400 [thread overview]
Message-ID: <20100519195717.2885.90799.stgit@localhost6.localdomain6> (raw)
Hi,
Here is a series of patches which improves perf probe to
add below features. I cleared some coding style issues.
- String support, which enables dynamic events to trace string
variables instead of its address.
- Fixed-index array entry support, which allows user to trace
an array entry with digit index, e.g. array[0].
- Global/static variable support, which allows user to trace
global or static variables, as same as local one.
TODOs (possible features):
- Support dynamic array-indexing (var[var2])
- Support force type-casting ((type)var)
- Show what deta-structure member is assigned to each argument.
- Better support for probes on modules
- More debugger like enhancements(%next, --disasm, etc.)
Thank you,
---
Masami Hiramatsu (4):
perf probe: Support static and global variables
perf probe: Support tracing an entry of array
perf probe: Support "string" type
tracing/kprobes: Support "string" type
Documentation/trace/kprobetrace.txt | 2
kernel/trace/trace_kprobe.c | 370 ++++++++++++++++++++++++-------
tools/perf/Documentation/perf-probe.txt | 4
tools/perf/util/probe-event.c | 71 ++++--
tools/perf/util/probe-event.h | 1
tools/perf/util/probe-finder.c | 192 +++++++++++++---
6 files changed, 498 insertions(+), 142 deletions(-)
--
Masami Hiramatsu
e-mail: mhiramat@redhat.com
next reply other threads:[~2010-05-19 19:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 19:57 Masami Hiramatsu [this message]
2010-05-19 19:57 ` [PATCH -tip 1/4] tracing/kprobes: Support "string" type Masami Hiramatsu
2010-07-06 8:37 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-05-19 19:57 ` [PATCH -tip 2/4] perf probe: " Masami Hiramatsu
2010-07-06 8:37 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-05-19 19:57 ` [PATCH -tip 3/4] perf probe: Support tracing an entry of array Masami Hiramatsu
2010-07-06 8:37 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-05-19 19:57 ` [PATCH -tip 4/4] perf probe: Support static and global variables Masami Hiramatsu
2010-07-06 8:38 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-07-05 14:30 ` [PATCH -tip 0/4] perf-probe updates: string support, etc Chase Douglas
2010-07-05 17:44 ` Arnaldo Carvalho de Melo
2010-07-06 0:47 ` Masami Hiramatsu
2010-07-06 5:04 ` Srikar Dronamraju
2010-07-06 0:54 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2010-05-18 2:49 Masami Hiramatsu
2010-05-18 2:49 ` Masami Hiramatsu
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=20100519195717.2885.90799.stgit@localhost6.localdomain6 \
--to=mhiramat@redhat.com \
--cc=acme@redhat.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--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 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 NNTP newsgroup(s).