From: Tom Zanussi <tzanussi@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, fweisbec@gmail.com, acme@ghostprotocols.net
Subject: [PATCH 0/9] perf-trace/scripting: script fixes
Date: Sun, 9 May 2010 23:46:51 -0500 [thread overview]
Message-ID: <1273466820-9330-1-git-send-email-tzanussi@gmail.com> (raw)
While testing the new 'trace events reordering' patches, I noticed
some problems with the current set of scripts, mostly annoying warning
messages, but a couple of real problems too.
Another annoyance, which I moved to verbose mode, was the display of
the script name on each invocation.
Anyway, after testing all the scripts in both normal and live mode, I
haven't seen any problems with the new event reordering patches...
Tom Zanussi (9):
perf/trace/scripting: failed-syscalls script cleanup
perf/trace/scripting: rw-by-pid script cleanup
perf/trace/scripting: rwtop script cleanup
perf/trace/scripting: wakeup-latency script cleanup
perf/trace/scripting: workqueue-stats script cleanup
perf/trace/scripting: don't show script start/stop messages by
default
perf/trace/scripting: failed-syscalls-by-pid script cleanup
perf/trace/scripting: syscall-counts-by-pid script cleanup
perf/trace/scripting: syscall-counts script cleanup
tools/perf/builtin-trace.c | 3 +
tools/perf/scripts/perl/bin/failed-syscalls-report | 2 +-
tools/perf/scripts/perl/failed-syscalls.pl | 6 ++-
tools/perf/scripts/perl/rw-by-pid.pl | 60 ++++++++++++--------
tools/perf/scripts/perl/rwtop.pl | 48 +++++++++++----
tools/perf/scripts/perl/wakeup-latency.pl | 12 +++-
tools/perf/scripts/perl/workqueue-stats.pl | 12 ++--
.../python/bin/failed-syscalls-by-pid-report | 2 +-
.../python/bin/syscall-counts-by-pid-report | 2 +-
.../perf/scripts/python/bin/syscall-counts-report | 2 +-
.../perf/util/scripting-engines/trace-event-perl.c | 3 -
.../util/scripting-engines/trace-event-python.c | 4 -
12 files changed, 98 insertions(+), 58 deletions(-)
next reply other threads:[~2010-05-10 4:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 4:46 Tom Zanussi [this message]
2010-05-10 4:46 ` [PATCH 1/9] perf/trace/scripting: failed-syscalls script cleanup Tom Zanussi
2010-05-10 4:46 ` [PATCH 2/9] perf/trace/scripting: rw-by-pid " Tom Zanussi
2010-05-10 4:46 ` [PATCH 3/9] perf/trace/scripting: rwtop " Tom Zanussi
2010-05-10 4:46 ` [PATCH 4/9] perf/trace/scripting: wakeup-latency " Tom Zanussi
2010-05-10 4:46 ` [PATCH 5/9] perf/trace/scripting: workqueue-stats " Tom Zanussi
2010-05-10 4:46 ` [PATCH 6/9] perf/trace/scripting: don't show script start/stop messages by default Tom Zanussi
2010-05-10 4:46 ` [PATCH 7/9] perf/trace/scripting: failed-syscalls-by-pid script cleanup Tom Zanussi
2010-05-10 4:46 ` [PATCH 8/9] perf/trace/scripting: syscall-counts-by-pid " Tom Zanussi
2010-05-10 4:47 ` [PATCH 9/9] perf/trace/scripting: syscall-counts " Tom Zanussi
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=1273466820-9330-1-git-send-email-tzanussi@gmail.com \
--to=tzanussi@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®