mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Tom Zanussi <tzanussi@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Keiichi KII <k-keiichi@bx.jp.nec.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL] Perf python scripting support
Date: Thu, 25 Feb 2010 04:42:31 +0100	[thread overview]
Message-ID: <1267069361-10909-1-git-send-regression-fweisbec@gmail.com> (raw)

Ingo,

Please pull the perf/core branch that can be found at:

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
	perf/core

I've left out the parts that deal with syscall nr to name
resolution as it would be nicer to implement it through events
injection instead of yet another debugfs file.

The reason I've made a separate patch to tag syscall_name()
helper as unavailable yet is that it makes it easily
revertable later, once it gets supported.

I've tested the whole and it works very well.

Thanks,
	Frederic
---

Tom Zanussi (9):
      perf/scripts: Fix supported language listing option
      perf/scripts: Fix bug in Util.pm
      perf/scripts: Move common code out of Perl-specific files
      perf/scripts: Move Perl scripting files to scripting-engines dir
      perf/scripts: Remove check-perf-trace from listed scripts
      perf/scripts: Add Python scripting engine
      perf/scripts: Add syscall tracing scripts
      perf/scripts: Remove unnecessary PyTuple resizes
      perf/scripts: Add perf-trace-python Documentation

Frederic Weisbecker (1):
      perf/scripts: Tag syscall_name helper as not yet available


 tools/perf/Documentation/perf-trace-perl.txt       |    2 +-
 tools/perf/Documentation/perf-trace-python.txt     |  625 ++++++++++++++++++
 tools/perf/Documentation/perf-trace.txt            |   15 +-
 tools/perf/Makefile                                |   33 +-
 tools/perf/builtin-trace.c                         |    5 +-
 tools/perf/scripts/perl/Perf-Trace-Util/Context.c  |    5 +-
 tools/perf/scripts/perl/Perf-Trace-Util/Context.xs |    3 +-
 .../perl/Perf-Trace-Util/lib/Perf/Trace/Util.pm    |    2 +-
 .../perf/scripts/perl/bin/check-perf-trace-record  |    7 +-
 .../perf/scripts/perl/bin/check-perf-trace-report  |    6 -
 tools/perf/scripts/perl/bin/failed-syscalls-record |    2 +
 tools/perf/scripts/perl/bin/failed-syscalls-report |    4 +
 tools/perf/scripts/perl/failed-syscalls.pl         |   38 ++
 .../perf/scripts/python/Perf-Trace-Util/Context.c  |   88 +++
 .../python/Perf-Trace-Util/lib/Perf/Trace/Core.py  |   91 +++
 .../python/Perf-Trace-Util/lib/Perf/Trace/Util.py  |   25 +
 .../python/bin/failed-syscalls-by-pid-record       |    2 +
 .../python/bin/failed-syscalls-by-pid-report       |    4 +
 .../python/bin/syscall-counts-by-pid-record        |    2 +
 .../python/bin/syscall-counts-by-pid-report        |    4 +
 .../perf/scripts/python/bin/syscall-counts-record  |    2 +
 .../perf/scripts/python/bin/syscall-counts-report  |    4 +
 tools/perf/scripts/python/check-perf-trace.py      |   83 +++
 .../perf/scripts/python/failed-syscalls-by-pid.py  |   68 ++
 tools/perf/scripts/python/syscall-counts-by-pid.py |   64 ++
 tools/perf/scripts/python/syscall-counts.py        |   58 ++
 .../perf/util/scripting-engines/trace-event-perl.c |  568 +++++++++++++++++
 .../util/scripting-engines/trace-event-python.c    |  573 +++++++++++++++++
 tools/perf/util/trace-event-parse.c                |   15 +
 tools/perf/util/trace-event-perl.c                 |  661 --------------------
 tools/perf/util/trace-event-perl.h                 |   55 --
 tools/perf/util/trace-event-scripting.c            |  167 +++++
 tools/perf/util/trace-event.h                      |   10 +-
 33 files changed, 2549 insertions(+), 742 deletions(-)

             reply	other threads:[~2010-02-25  3:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25  3:42 Frederic Weisbecker [this message]
2010-02-25  3:42 ` [PATCH 01/10] perf/scripts: Fix supported language listing option Frederic Weisbecker
2010-02-25  3:42 ` [PATCH 02/10] perf/scripts: Fix bug in Util.pm Frederic Weisbecker
2010-02-25  3:42 ` [PATCH 03/10] perf/scripts: Move common code out of Perl-specific files Frederic Weisbecker
2010-02-25  3:42 ` [PATCH 04/10] perf/scripts: Move Perl scripting files to scripting-engines dir Frederic Weisbecker
2010-02-25  3:42 ` [PATCH 05/10] perf/scripts: Remove check-perf-trace from listed scripts Frederic Weisbecker
2010-02-25  3:42 ` [PATCH 06/10] perf/scripts: Add Python scripting engine Frederic Weisbecker
2010-02-25  3:42 ` [PATCH 07/10] perf/scripts: Add syscall tracing scripts Frederic Weisbecker
2010-02-25  3:42 ` [PATCH 08/10] perf/scripts: Remove unnecessary PyTuple resizes Frederic Weisbecker
2010-02-25  3:42 ` [PATCH 09/10] perf/scripts: Add perf-trace-python Documentation Frederic Weisbecker
2010-02-25  3:42 ` [PATCH 10/10] perf/scripts: Tag syscall_name helper as not yet available Frederic Weisbecker
2010-02-25  7:32 ` [GIT PULL] Perf python scripting support 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=1267069361-10909-1-git-send-regression-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=k-keiichi@bx.jp.nec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=rostedt@goodmis.org \
    --cc=tzanussi@gmail.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

all inboxes | Powered by JetHome®