All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Tony Jones <tonyj@suse.de>, linux-kernel@vger.kernel.org
Cc: acme@kernel.org, linux-perf-users@vger.kernel.org,
	Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 5/7] perf script python: add Python3 support to intel-pt-events.py
Date: Wed, 6 Mar 2019 11:28:35 +0200	[thread overview]
Message-ID: <d3920c9a-3990-6111-ca4f-58d96a929bf4@intel.com> (raw)
In-Reply-To: <fd26acf9-0c0f-717f-9664-a3c33043ce19@suse.de>

On 5/03/19 6:19 PM, Tony Jones wrote:
> On 3/5/19 8:10 AM, Tony Jones wrote:
> 
>>
>> Sure enough, I managed to attach the wrong patch. Sorry. I'll attach revised (v3) 
>> to this thread as the change is trivial.
> 
> From: Tony Jones <tonyj@suse.de>
> Date: Tue, 05 Mar 2019 08:31:30 -0800
> Subject: [PATCH v3] perf script python: add Python3 support to intel-pt-events.py
> 
> Support both Python2 and Python3 in the intel-pt-events.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.
> 
> The use of 'from __future__' implies the minimum supported Python2 version
> is now v2.6
> 
> Signed-off-by: Tony Jones <tonyj@suse.de>
> Signed-off-by: Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>
> Cc: Adrian Hunter <adrian.hunter@intel.com>

Acked-by: Adrian Hunter <adrian.hunter@intel.com>

> ---
>  tools/perf/scripts/python/intel-pt-events.py |   32 ++++++++++++++++-----------
>  1 file changed, 19 insertions(+), 13 deletions(-)
> 
> --- a/tools/perf/scripts/python/intel-pt-events.py
> +++ b/tools/perf/scripts/python/intel-pt-events.py
> @@ -10,6 +10,8 @@
>  # FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
>  # more details.
>  
> +from __future__ import print_function
> +
>  import os
>  import sys
>  import struct
> @@ -22,34 +24,34 @@ sys.path.append(os.environ['PERF_EXEC_PA
>  #from Core import *
>  
>  def trace_begin():
> -	print "Intel PT Power Events and PTWRITE"
> +	print("Intel PT Power Events and PTWRITE")
>  
>  def trace_end():
> -	print "End"
> +	print("End")
>  
>  def trace_unhandled(event_name, context, event_fields_dict):
> -		print ' '.join(['%s=%s'%(k,str(v))for k,v in sorted(event_fields_dict.items())])
> +		print(' '.join(['%s=%s'%(k,str(v))for k,v in sorted(event_fields_dict.items())]))
>  
>  def print_ptwrite(raw_buf):
>  	data = struct.unpack_from("<IQ", raw_buf)
>  	flags = data[0]
>  	payload = data[1]
>  	exact_ip = flags & 1
> -	print "IP: %u payload: %#x" % (exact_ip, payload),
> +	print("IP: %u payload: %#x" % (exact_ip, payload), end=' ')
>  
>  def print_cbr(raw_buf):
>  	data = struct.unpack_from("<BBBBII", raw_buf)
>  	cbr = data[0]
>  	f = (data[4] + 500) / 1000
>  	p = ((cbr * 1000 / data[2]) + 5) / 10
> -	print "%3u  freq: %4u MHz  (%3u%%)" % (cbr, f, p),
> +	print("%3u  freq: %4u MHz  (%3u%%)" % (cbr, f, p), end=' ')
>  
>  def print_mwait(raw_buf):
>  	data = struct.unpack_from("<IQ", raw_buf)
>  	payload = data[1]
>  	hints = payload & 0xff
>  	extensions = (payload >> 32) & 0x3
> -	print "hints: %#x extensions: %#x" % (hints, extensions),
> +	print("hints: %#x extensions: %#x" % (hints, extensions), end=' ')
>  
>  def print_pwre(raw_buf):
>  	data = struct.unpack_from("<IQ", raw_buf)
> @@ -57,13 +59,14 @@ def print_pwre(raw_buf):
>  	hw = (payload >> 7) & 1
>  	cstate = (payload >> 12) & 0xf
>  	subcstate = (payload >> 8) & 0xf
> -	print "hw: %u cstate: %u sub-cstate: %u" % (hw, cstate, subcstate),
> +	print("hw: %u cstate: %u sub-cstate: %u" % (hw, cstate, subcstate),
> +		end=' ')
>  
>  def print_exstop(raw_buf):
>  	data = struct.unpack_from("<I", raw_buf)
>  	flags = data[0]
>  	exact_ip = flags & 1
> -	print "IP: %u" % (exact_ip),
> +	print("IP: %u" % (exact_ip), end=' ')
>  
>  def print_pwrx(raw_buf):
>  	data = struct.unpack_from("<IQ", raw_buf)
> @@ -71,18 +74,21 @@ def print_pwrx(raw_buf):
>  	deepest_cstate = payload & 0xf
>  	last_cstate = (payload >> 4) & 0xf
>  	wake_reason = (payload >> 8) & 0xf
> -	print "deepest cstate: %u last cstate: %u wake reason: %#x" % (deepest_cstate, last_cstate, wake_reason),
> +	print("deepest cstate: %u last cstate: %u wake reason: %#x" %
> +		(deepest_cstate, last_cstate, wake_reason), end=' ')
>  
>  def print_common_start(comm, sample, name):
>  	ts = sample["time"]
>  	cpu = sample["cpu"]
>  	pid = sample["pid"]
>  	tid = sample["tid"]
> -	print "%16s %5u/%-5u [%03u] %9u.%09u %7s:" % (comm, pid, tid, cpu, ts / 1000000000, ts %1000000000, name),
> +	print("%16s %5u/%-5u [%03u] %9u.%09u %7s:" %
> +		(comm, pid, tid, cpu, ts / 1000000000, ts %1000000000, name),
> +		end=' ')
>  
>  def print_common_ip(sample, symbol, dso):
>  	ip = sample["ip"]
> -	print "%16x %s (%s)" % (ip, symbol, dso)
> +	print("%16x %s (%s)" % (ip, symbol, dso))
>  
>  def process_event(param_dict):
>  	event_attr = param_dict["attr"]
> @@ -92,12 +98,12 @@ def process_event(param_dict):
>  	name	   = param_dict["ev_name"]
>  
>  	# Symbol and dso info are not always resolved
> -	if (param_dict.has_key("dso")):
> +	if "dso" in param_dict:
>  		dso = param_dict["dso"]
>  	else:
>  		dso = "[unknown]"
>  
> -	if (param_dict.has_key("symbol")):
> +	if "symbol" in param_dict:
>  		symbol = param_dict["symbol"]
>  	else:
>  		symbol = "[unknown]"
> 


  reply	other threads:[~2019-03-06  9:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02  1:18 [PATCH v2 0/7] perf script python: add Python3 support Tony Jones
2019-03-02  1:18 ` [PATCH v2 1/7] perf script python: remove mixed indentation Tony Jones
2019-03-05 10:39   ` Adrian Hunter
2019-03-06 21:09   ` Arnaldo Carvalho de Melo
2019-03-09 20:02   ` [tip:perf/urgent] perf script python: Remove " tip-bot for Tony Jones
2019-03-02  1:18 ` [PATCH v2 2/7] perf script python: add Python3 support to futex-contention.py Tony Jones
2019-03-06 21:11   ` Arnaldo Carvalho de Melo
2019-03-09 20:02   ` [tip:perf/urgent] perf script python: Add " tip-bot for Tony Jones
2019-03-02  1:18 ` [PATCH v2 3/7] perf script python: add Python3 support to check-perf-trace.py Tony Jones
2019-03-06 21:11   ` Arnaldo Carvalho de Melo
2019-03-09 20:03   ` [tip:perf/urgent] " tip-bot for Tony Jones
2019-03-02  1:19 ` [PATCH v2 4/7] perf script python: add Python3 support to event_analyzing_sample.py Tony Jones
2019-03-06 21:11   ` Arnaldo Carvalho de Melo
2019-03-09 20:04   ` [tip:perf/urgent] perf script python: Add " tip-bot for Tony Jones
2019-03-02  1:19 ` [PATCH v2 5/7] perf script python: add Python3 support to intel-pt-events.py Tony Jones
2019-03-05 10:16   ` Adrian Hunter
2019-03-05 15:02     ` Tony Jones
2019-03-05 16:10       ` Tony Jones
2019-03-05 16:19         ` Tony Jones
2019-03-06  9:28           ` Adrian Hunter [this message]
2019-03-06 21:12             ` Arnaldo Carvalho de Melo
2019-03-09 20:04           ` [tip:perf/urgent] perf script python: Add " tip-bot for Tony Jones
2019-03-02  1:19 ` [PATCH v2 6/7] perf script python: add Python3 support to sql scripts Tony Jones
2019-03-06  9:26   ` Adrian Hunter
2019-03-06 16:32     ` Tony Jones
2019-03-07 18:51       ` Arnaldo Carvalho de Melo
2019-03-08  9:47         ` Adrian Hunter
2019-03-08 14:36           ` Arnaldo Carvalho de Melo
2019-03-02  1:19 ` [PATCH v2 7/7] perf script python: add printdate function to SQL exporters Tony Jones
2019-03-06 21:13   ` Arnaldo Carvalho de Melo
2019-03-08 12:50     ` Adrian Hunter
2019-03-05  9:55 ` [PATCH v2 0/7] perf script python: add Python3 support Adrian Hunter
2019-03-05 14:53   ` Tony Jones
2019-03-05 15:18     ` 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=d3920c9a-3990-6111-ca4f-58d96a929bf4@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=s1seetee@linux.vnet.ibm.com \
    --cc=tonyj@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.