From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>, lkml<linux-kernel@vger.kernel.org>
Cc: Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Jim Keniston <jkenisto@us.ibm.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
Jason Baron <jbaron@redhat.com>,
"K.Prasad" <prasad@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Ulrich Drepper <drepper@redhat.com>,
Roland McGrath <roland@redhat.com>,
Mike Galbraith <efault@gmx.de>,
systemtap<systemtap@sources.redhat.com>,
DLE<dle-develop@lists.sourceforge.net>
Subject: [PATCH -tip 0/9] perf-probe updates - use elfutils and introduce lazy matching
Date: Thu, 18 Feb 2010 23:20:00 -0000 [thread overview]
Message-ID: <20100218232701.21679.5195.stgit@dhcp-100-2-132.bos.redhat.com> (raw)
Hi Ingo,
Here are several bugfixes and updates of perf-probe.
This updates includes moving onto elfutils-libdw and
the lazy line matching support which you had mentioned :-)
elfutils library is developed closely with gcc team,
and it is simple and fast dwarf analysis library.
lazy-matching is similar to glob matching but ignoring
spaces in both of target and pattern.
This is updated todo list. Most of them are related
to the 'type' support.
Long-term TODOs (future features):
- Enhance probe-finder to decode call frame instructions.
- Support sys_perf_counter_open (for non-root users)
- Support tracing static variables (non global)
- Support variable types from debuginfo (e.g. char, int, ...)
- Support fields of data structures (var->field)
- Support array (var[N])
- Support dynamic array-indexing (var[var2])
- Support string/dynamic arrays (*var, var[N..M])
- Support force type-casting ((type)var)
- Support the type of return value
Miscs:
- Better support for probes on modules
- --list option shows the file-name/line-number of each events.
Thank you,
---
Masami Hiramatsu (9):
perf probe: Add lazy line matching support
perf probe: show more lines after last line
perf probe: Check function address range strictly in line finder
perf probe: Use libdw callback routines
perf probe: Use elfutils-libdw for analyzing debuginfo
perf probe: Rename probe finder functions
perf probe: Fix bugs in line range finder
perf probe: Update perf probe document
perf probe: Do not show --line option without dwarf support
tools/perf/Documentation/perf-probe.txt | 58 ++
tools/perf/Makefile | 10
tools/perf/builtin-probe.c | 36 +
tools/perf/util/probe-event.c | 55 +-
tools/perf/util/probe-finder.c | 994 ++++++++++++++-----------------
tools/perf/util/probe-finder.h | 53 +-
tools/perf/util/string.c | 55 +-
tools/perf/util/string.h | 1
8 files changed, 639 insertions(+), 623 deletions(-)
--
Masami Hiramatsu
e-mail: mhiramat@redhat.com
next reply other threads:[~2010-02-18 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 23:20 Masami Hiramatsu [this message]
2010-02-18 23:20 ` [PATCH -tip 1/9] perf probe: Do not show --line option without dwarf support Masami Hiramatsu
2010-02-18 23:20 ` [PATCH -tip 4/9] perf probe: Rename probe finder functions Masami Hiramatsu
2010-02-18 23:20 ` [PATCH -tip 3/9] perf probe: Fix bugs in line range finder Masami Hiramatsu
2010-02-18 23:20 ` [PATCH -tip 2/9] perf probe: Update perf probe document Masami Hiramatsu
2010-02-18 23:21 ` [PATCH -tip 6/9] perf probe: Use libdw callback routines Masami Hiramatsu
2010-02-18 23:21 ` [PATCH -tip 8/9] perf probe: show more lines after last line Masami Hiramatsu
2010-02-18 23:21 ` [PATCH -tip 7/9] perf probe: Check function address range strictly in line finder Masami Hiramatsu
2010-02-18 23:21 ` [PATCH -tip 5/9] perf probe: Use elfutils-libdw for analyzing debuginfo Masami Hiramatsu
2010-02-21 21:14 ` [Dle-develop] " Masami Hiramatsu
2010-02-22 10:29 ` Ingo Molnar
2010-02-18 23:22 ` [PATCH -tip 9/9] perf probe: Add lazy line matching support 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=20100218232701.21679.5195.stgit@dhcp-100-2-132.bos.redhat.com \
--to=mhiramat@redhat.com \
--cc=acme@redhat.com \
--cc=ananth@in.ibm.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=drepper@redhat.com \
--cc=efault@gmx.de \
--cc=fche@redhat.com \
--cc=hch@infradead.org \
--cc=jbaron@redhat.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--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 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).