From: Frederic Weisbecker on 24 Feb 2010 22:50 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(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Pages: 1 Prev: [git patch] libata bug fix Next: cs5535_gpio: gpio_chip.get should return the input value |