mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 00/10] perf-probe updates - data-structure support, etc.
Date: Tue, 16 Mar 2010 18:05:15 -0400	[thread overview]
Message-ID: <20100316220515.32050.82185.stgit@localhost6.localdomain6> (raw)

Hi Ingo,

Here are several updates of perf-probe.
This updates includes data structure accessing support
--list option enhancement and --dry-run option support.

- --dry-run allows users to run perf-probe just for checking
  that the command works correctly.

- --list option enhancement allows user to check where the
  probes are put on (with filename/line number).

- data structure accessing support allows user to trace
  the contents of local variables/function parameters.

Long-term TODOs (future features):
  - Enhance probe-finder to decode call frame instructions.
  - Support tracing static variables (non global)
  - Support variable basic types from debuginfo (e.g. char, int, ...)
  - Support array element (var[N])
  - Support string/dynamic arrays (*var, var[N..M])
  - Support the type of return value
  - Support force type-casting ((type)var)
  - Support sys_perf_counter_open (for non-root users)
  - Support dynamic array-indexing (var[var2])

Miscs:
  - Better support for probes on modules
  - More debugger like enhancements(%next, --disasm, etc.)


Thank you,

---

Masami Hiramatsu (10):
      perf probe: Accessing members in data structures
      perf probe: List probes with line number and file name
      perf probe: Introduce kprobe_trace_event and perf_probe_event
      perf probe: Add --dry-run option
      perf probe: Introduce die_find_child() function
      perf probe: Rename some die_get_* functions
      perf probe: Rename session to param
      perf probe: Move add-probe routine under util/
      perf probe: Use wrapper functions
      perf tools: Introduce xzalloc() for detecting out of memory


 tools/perf/Documentation/perf-probe.txt |    5 
 tools/perf/builtin-probe.c              |  191 +------
 tools/perf/util/probe-event.c           |  830 +++++++++++++++++++++++--------
 tools/perf/util/probe-event.h           |  123 ++++-
 tools/perf/util/probe-finder.c          |  459 ++++++++++++-----
 tools/perf/util/probe-finder.h          |   60 +-
 tools/perf/util/util.h                  |    7 
 7 files changed, 1115 insertions(+), 560 deletions(-)

-- 
Masami Hiramatsu
e-mail: mhiramat@redhat.com

             reply	other threads:[~2010-03-16 21:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 22:05 Masami Hiramatsu [this message]
2010-03-16 22:05 ` [PATCH -tip 01/10] perf tools: Introduce xzalloc() for detecting out of memory Masami Hiramatsu
2010-03-17 11:27   ` [tip:perf/core] perf tools: Introduce xzalloc() for detecting out of memory conditions tip-bot for Masami Hiramatsu
2010-03-16 22:05 ` [PATCH -tip 02/10] perf probe: Use wrapper functions Masami Hiramatsu
2010-03-17 11:27   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-03-16 22:05 ` [PATCH -tip 03/10] perf probe: Move add-probe routine under util/ Masami Hiramatsu
2010-03-17 11:28   ` [tip:perf/core] perf probe: Move add-probe routine to util/ tip-bot for Masami Hiramatsu
2010-03-16 22:05 ` [PATCH -tip 04/10] perf probe: Rename session to param Masami Hiramatsu
2010-03-17 11:28   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-03-16 22:05 ` [PATCH -tip 05/10] perf probe: Rename some die_get_* functions Masami Hiramatsu
2010-03-17 11:28   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-03-16 22:05 ` [PATCH -tip 06/10] perf probe: Introduce die_find_child() function Masami Hiramatsu
2010-03-17 11:29   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-03-16 22:06 ` [PATCH -tip 07/10] perf probe: Add --dry-run option Masami Hiramatsu
2010-03-17 11:29   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-03-16 22:06 ` [PATCH -tip 08/10] perf probe: Introduce kprobe_trace_event and perf_probe_event Masami Hiramatsu
2010-03-17 11:29   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-03-17 11:30   ` [tip:perf/core] perf probe: Fix !dwarf build tip-bot for Ingo Molnar
2010-03-17 14:14     ` Masami Hiramatsu
2010-03-18 17:38   ` [tip:perf/core] perf events: Fix false positive build warning with older GCC's tip-bot for Ingo Molnar
2010-03-18 20:03     ` Masami Hiramatsu
2010-03-16 22:06 ` [PATCH -tip 09/10] perf probe: List probes with line number and file name Masami Hiramatsu
2010-03-17 11:29   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-03-16 22:06 ` [PATCH -tip 10/10] perf probe: Accessing members in data structures Masami Hiramatsu
2010-03-17 10:25   ` Mark Wielaard
2010-03-17 19:14     ` Masami Hiramatsu
2010-03-18  3:28       ` Frederic Weisbecker
2010-03-20  4:20         ` Masami Hiramatsu
2010-03-23 15:55         ` Peter Zijlstra
2010-03-23 16:27           ` Arnaldo Carvalho de Melo
2010-03-17 11:30   ` [tip:perf/core] perf probe: Add data structure member access support tip-bot for Masami Hiramatsu
2010-03-17 10:34 ` [PATCH -tip 00/10] perf-probe updates - data-structure support, etc Ingo Molnar

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=20100316220515.32050.82185.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

Powered by JetHome