From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>, lkml<linux-kernel@vger.kernel.org>
Cc: systemtap<systemtap@sources.redhat.com>,
DLE<dle-develop@lists.sourceforge.net>
Subject: [PATCH -tip v2 0/9] perf-probe updates - use elfutils and introduce lazy matching
Date: Mon, 22 Feb 2010 22:49:00 -0000 [thread overview]
Message-ID: <20100222225320.20686.17645.stgit@localhost6.localdomain6> (raw)
Hi Ingo,
Here are several bugfixes and updates of perf-probe (v2).
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.
Changes in v2:
(Fixed bugs on x86-64)
- Fix a type-casting bug in Makefile.
- Cast Dwarf_Addr/Dwarf_Word to unsigned long long for
printf-formats.
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.
- More debugger like enhancements(%next, --disasm, etc.)
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 | 1002 ++++++++++++++-----------------
tools/perf/util/probe-finder.h | 53 +-
tools/perf/util/string.c | 55 +-
tools/perf/util/string.h | 1
8 files changed, 644 insertions(+), 626 deletions(-)
--
Masami Hiramatsu
e-mail: mhiramat@redhat.com
next reply other threads:[~2010-02-22 22:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 22:49 Masami Hiramatsu [this message]
2010-02-22 22:49 ` [PATCH -tip v2 1/9] perf probe: Do not show --line option without dwarf support Masami Hiramatsu
2010-02-22 22:49 ` [PATCH -tip v2 3/9] perf probe: Fix bugs in line range finder Masami Hiramatsu
2010-02-22 22:49 ` [PATCH -tip v2 4/9] perf probe: Rename probe finder functions Masami Hiramatsu
2010-02-22 22:49 ` [PATCH -tip v2 2/9] perf probe: Update perf probe document Masami Hiramatsu
2010-02-22 22:50 ` [PATCH -tip v2 7/9] perf probe: Check function address range strictly in line finder Masami Hiramatsu
2010-02-22 22:50 ` [PATCH -tip v2 6/9] perf probe: Use libdw callback routines Masami Hiramatsu
2010-02-22 22:50 ` [PATCH -tip v2 5/9] perf probe: Use elfutils-libdw for analyzing debuginfo Masami Hiramatsu
2010-02-22 23:08 ` Ulrich Drepper
2010-02-22 23:13 ` Masami Hiramatsu
2010-02-22 23:18 ` Masami Hiramatsu
2010-02-22 23:20 ` Ulrich Drepper
2010-02-22 23:19 ` Ulrich Drepper
2010-02-22 22:50 ` [PATCH -tip v2 8/9] perf probe: show more lines after last line Masami Hiramatsu
2010-02-22 22:51 ` [PATCH -tip v2 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=20100222225320.20686.17645.stgit@localhost6.localdomain6 \
--to=mhiramat@redhat.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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).