From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Tony Jones <tonyj@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>,
Tom Zanussi <tzanussi@gmail.com>
Subject: Re: [PATCH 02/15] perf script python: add Python3 support to check-perf-trace.py
Date: Mon, 25 Feb 2019 11:05:35 -0300 [thread overview]
Message-ID: <20190225140535.GE31136@kernel.org> (raw)
In-Reply-To: <20190222230619.17887-3-tonyj@suse.de>
Em Fri, Feb 22, 2019 at 03:06:06PM -0800, Tony Jones escreveu:
> Support both Python 2 and Python 3 in the check-perf-trace.py script.
>
> There may be differences in the ordering of output lines due to
> differences in dictionary ordering etc. However the format within lines
> should be unchanged.
>
> Also correct inconsistent indentation which was being flagged by Python3.
When we have "Also" in a patch, usually it need to be split :-)
- Arnaldo
> The use of from __future__ implies the minimum supported version of
> Python2 is now v2.6
>
> Signed-off-by: Tony Jones <tonyj@suse.de>
> Signed-off-by: Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>
> Cc: Tom Zanussi <tzanussi@gmail.com>
> ---
> tools/perf/scripts/python/check-perf-trace.py | 68 ++++++++++---------
> 1 file changed, 36 insertions(+), 32 deletions(-)
>
> diff --git a/tools/perf/scripts/python/check-perf-trace.py b/tools/perf/scripts/python/check-perf-trace.py
> index 334599c6032c..2851cf0e6b4b 100644
> --- a/tools/perf/scripts/python/check-perf-trace.py
> +++ b/tools/perf/scripts/python/check-perf-trace.py
> @@ -7,11 +7,13 @@
> # events, etc. Basically, if this script runs successfully and
> # displays expected results, Python scripting support should be ok.
>
> +from __future__ import print_function
> +
> import os
> import sys
>
> -sys.path.append(os.environ['PERF_EXEC_PATH'] + \
> - '/scripts/python/Perf-Trace-Util/lib/Perf/Trace')
> +sys.path.append(os.environ['PERF_EXEC_PATH'] +
> + '/scripts/python/Perf-Trace-Util/lib/Perf/Trace')
>
> from Core import *
> from perf_trace_context import *
> @@ -19,37 +21,38 @@ from perf_trace_context import *
> unhandled = autodict()
>
> def trace_begin():
> - print "trace_begin"
> - pass
> + print("trace_begin")
> + pass
>
> def trace_end():
> - print_unhandled()
> + print_unhandled()
>
> def irq__softirq_entry(event_name, context, common_cpu,
> - common_secs, common_nsecs, common_pid, common_comm,
> - common_callchain, vec):
> - print_header(event_name, common_cpu, common_secs, common_nsecs,
> - common_pid, common_comm)
> + common_secs, common_nsecs, common_pid, common_comm,
> + common_callchain, vec):
> +
> + print_header(event_name, common_cpu, common_secs, common_nsecs,
> + common_pid, common_comm)
>
> - print_uncommon(context)
> + print_uncommon(context)
>
> - print "vec=%s\n" % \
> - (symbol_str("irq__softirq_entry", "vec", vec)),
> + print("vec=%s" %
> + (symbol_str("irq__softirq_entry", "vec", vec)))
>
> def kmem__kmalloc(event_name, context, common_cpu,
> - common_secs, common_nsecs, common_pid, common_comm,
> - common_callchain, call_site, ptr, bytes_req, bytes_alloc,
> - gfp_flags):
> - print_header(event_name, common_cpu, common_secs, common_nsecs,
> - common_pid, common_comm)
> + common_secs, common_nsecs, common_pid, common_comm,
> + common_callchain, call_site, ptr, bytes_req, bytes_alloc,
> + gfp_flags):
>
> - print_uncommon(context)
> + print_header(event_name, common_cpu, common_secs, common_nsecs,
> + common_pid, common_comm)
>
> - print "call_site=%u, ptr=%u, bytes_req=%u, " \
> - "bytes_alloc=%u, gfp_flags=%s\n" % \
> - (call_site, ptr, bytes_req, bytes_alloc,
> + print_uncommon(context)
>
> - flag_str("kmem__kmalloc", "gfp_flags", gfp_flags)),
> + print("call_site=%u, ptr=%u, bytes_req=%u, "
> + "bytes_alloc=%u, gfp_flags=%s\n" %
> + (call_site, ptr, bytes_req, bytes_alloc,
> + flag_str("kmem__kmalloc", "gfp_flags", gfp_flags))),
>
> def trace_unhandled(event_name, context, event_fields_dict):
> try:
> @@ -58,25 +61,26 @@ def trace_unhandled(event_name, context, event_fields_dict):
> unhandled[event_name] = 1
>
> def print_header(event_name, cpu, secs, nsecs, pid, comm):
> - print "%-20s %5u %05u.%09u %8u %-20s " % \
> - (event_name, cpu, secs, nsecs, pid, comm),
> + print("%-20s %5u %05u.%09u %8u %-20s " %
> + (event_name, cpu, secs, nsecs, pid, comm),
> + end='')
>
> # print trace fields not included in handler args
> def print_uncommon(context):
> - print "common_preempt_count=%d, common_flags=%s, common_lock_depth=%d, " \
> - % (common_pc(context), trace_flag_str(common_flags(context)), \
> - common_lock_depth(context))
> + print("common_preempt_count=%d, common_flags=%s, common_lock_depth=%d, " %
> + (common_pc(context), trace_flag_str(common_flags(context)),
> + common_lock_depth(context))),
>
> def print_unhandled():
> keys = unhandled.keys()
> if not keys:
> return
>
> - print "\nunhandled events:\n\n",
> + print("\nunhandled events:\n")
>
> - print "%-40s %10s\n" % ("event", "count"),
> - print "%-40s %10s\n" % ("----------------------------------------", \
> - "-----------"),
> + print("%-40s %10s" % ("event", "count"))
> + print("%-40s %10s" % ("----------------------------------------",
> + "-----------"))
>
> for event_name in keys:
> - print "%-40s %10d\n" % (event_name, unhandled[event_name])
> + print("%-40s %10d\n" % (event_name, unhandled[event_name]))
> --
> 2.20.1
--
- Arnaldo
next prev parent reply other threads:[~2019-02-25 14:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 23:06 [PATCH 00/15] perf script python: add Python3 support Tony Jones
2019-02-22 23:06 ` [PATCH 01/15] perf script python: add Python3 support to netdev-times.py Tony Jones
2019-02-22 23:06 ` [PATCH 02/15] perf script python: add Python3 support to check-perf-trace.py Tony Jones
2019-02-25 14:05 ` Arnaldo Carvalho de Melo [this message]
2019-02-25 18:05 ` Tony Jones
2019-02-22 23:06 ` [PATCH 03/15] perf script python: add Python3 support to event_analyzing_sample.py Tony Jones
2019-02-25 14:08 ` Arnaldo Carvalho de Melo
2019-02-22 23:06 ` [PATCH 04/15] perf script python: add Python3 support to failed-syscalls-by-pid.py Tony Jones
2019-02-25 14:09 ` Arnaldo Carvalho de Melo
2019-02-22 23:06 ` [PATCH 05/15] perf script python: add Python3 support to futex-contention.py Tony Jones
2019-02-22 23:06 ` [PATCH 06/15] perf script python: add Python3 support to intel-pt-events.py Tony Jones
2019-02-25 7:07 ` Adrian Hunter
2019-02-25 14:03 ` Arnaldo Carvalho de Melo
2019-02-25 17:18 ` Tony Jones
2019-02-22 23:06 ` [PATCH 07/15] perf script python: add Python3 support to mem-phys-addr.py Tony Jones
2019-02-22 23:06 ` [PATCH 08/15] perf script python: add Python3 support to net_dropmonitor.py Tony Jones
2019-02-25 12:37 ` Neil Horman
2019-02-25 14:43 ` Arnaldo Carvalho de Melo
2019-02-22 23:06 ` [PATCH 09/15] perf script python: add Python3 support to powerpc-hcalls.py Tony Jones
2019-02-25 14:44 ` Arnaldo Carvalho de Melo
2019-02-22 23:06 ` [PATCH 10/15] perf script python: add Python3 support to sctop.py Tony Jones
2019-02-25 14:44 ` Arnaldo Carvalho de Melo
2019-02-22 23:06 ` [PATCH 11/15] perf script python: add Python3 support to stackcollapse.py Tony Jones
2019-02-25 14:46 ` Arnaldo Carvalho de Melo
2019-02-22 23:06 ` [PATCH 12/15] perf script python: add Python3 support to stat-cpi.py Tony Jones
2019-02-25 14:46 ` Arnaldo Carvalho de Melo
2019-02-22 23:06 ` [PATCH 13/15] perf script python: add Python3 support to syscall-counts.py Tony Jones
2019-02-25 14:47 ` Arnaldo Carvalho de Melo
2019-02-22 23:06 ` [PATCH 14/15] perf script python: add Python3 support to syscall-counts-by-pid.py Tony Jones
2019-02-25 14:48 ` Arnaldo Carvalho de Melo
2019-02-22 23:06 ` [PATCH 15/15] perf script python: add Python3 support to sql scripts Tony Jones
2019-02-25 14:51 ` Arnaldo Carvalho de Melo
2019-02-25 14:54 ` Arnaldo Carvalho de Melo
2019-02-25 17:20 ` Tony Jones
2019-02-23 21:06 ` [PATCH 00/15] perf script python: add Python3 support Tony Jones
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=20190225140535.GE31136@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=s1seetee@linux.vnet.ibm.com \
--cc=tonyj@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).