perf/scripts: Tuple was set from long in both branches in python_process_event()
authorTom Zanussi <tzanussi@gmail.com>
Fri, 2 Apr 2010 04:58:25 +0000 (23:58 -0500)
committerIngo Molnar <mingo@elte.hu>
Fri, 2 Apr 2010 19:32:16 +0000 (21:32 +0200)
commitb1dcc03cb8ee0f5718491e8c518257238dc64e00
tree72b6e2279e0bfa6af63c76b69220634c0ca39cbb
parent8bb39f9aa068262732fe44b965d7a6eb5a5a7d67
perf/scripts: Tuple was set from long in both branches in python_process_event()

This is a fix to the signed/unsigned field handling in the
Python scripting engine, based on a patch from Roel Kluin.

Basically, Python wants to use a PyInt (which is internally a
long) if it can i.e. if the value will fit into that type.  If
not, it stores it into a PyLong, which isn't actually a long,
but an arbitrary-precision integer variable.

The code below is similar to to what Python does internally, and
it seems to work as expected on the x86 and x86_64 sytems I
tested it on.

Signed-off-by: Tom Zanussi <tzanussi@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Roel Kluin <roel.kluin@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: rostedt@goodmis.org
LKML-Reference: <1270184305.6422.10.camel@tropicana>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
tools/perf/util/scripting-engines/trace-event-python.c