hi,
adding support to access tracepoint fields in python scripts.
v3 changes:
- once again fixed is_printable_array [Steven]
- patch 3/3 already merged
- added new patch 3/3 with automated test for is_printable_array
v2 changes:
- most of the patches is already pulled in,
this is just leftover
- fixed is_printable_array [Steven]
- making is_printable_array global
- attached unrelated fix 3/3
With this patchset it's possible to access tracepoint fields
in event python object like:
print "time %u prev_comm=%s prev_pid=%d prev_prio=%d prev_state=0x%x ==>
next_comm=%s next_pid=%d next_prio=%d" % (
event.sample_time,
event.prev_comm,
event.prev_pid,
event.prev_prio,
event.prev_state,
event.next_comm,
event.next_pid,
event.next_prio)
Also available in:
git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
perf/fixes
thanks,
jirka
---
Jiri Olsa (3):
perf script python: Fix string vs byte array resolving
perf tools: Make is_printable_array global
perf tests: Add is_printable_array test
tools/perf/tests/Build | 1 +
tools/perf/tests/builtin-test.c | 4 ++++
tools/perf/tests/is_printable_array.c | 36
++++++++++++++++++++++++++++++++++++
tools/perf/tests/tests.h | 1 +
tools/perf/util/python.c | 12 ------------
tools/perf/util/scripting-engines/trace-event-python.c | 25
++++++++++++++++++-------
tools/perf/util/util.c | 16 ++++++++++++++++
tools/perf/util/util.h | 1 +
8 files changed, 77 insertions(+), 19 deletions(-)
create mode 100644 tools/perf/tests/is_printable_array.c
