LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jeremy Cline <jeremy@jcline.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
"Herton R . Krzesinski" <herton@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeremy Cline <jeremy@jcline.org>
Subject: [PATCH 0/8] Improve Python 3 support in perf
Date: Tue, 8 May 2018 21:27:42 +0000 [thread overview]
Message-ID: <0100016341a7217a-d48a8d8a-c7ed-4857-82ef-9e2e599364e2-000000@email.amazonses.com> (raw)
Hi folks,
This patch set adds Python 3 support to a number of perf scripts,
including those generated by "perf script -g python", without breaking
Python 2 compatibility.
Jeremy Cline (8):
perf tools: Generate a Python script compatible with Python 2 and 3
perf scripts python: Add Python 3 support to Core.py
perf scripts python: Add Python 3 support to SchedGui.py
perf scripts python: Add Python 3 support to Util.py
perf scripts python: Add Python 3 support to EventClass.py
perf scripts python: Add Python 3 support to sched-migration.py
perf scripts python: Add Python 3 support to stat-cpi.py
perf tests: Add Python 3 support to attr.py
.../Perf-Trace-Util/lib/Perf/Trace/Core.py | 40 ++++++++-----------
.../lib/Perf/Trace/EventClass.py | 4 +-
.../lib/Perf/Trace/SchedGui.py | 2 +-
.../Perf-Trace-Util/lib/Perf/Trace/Util.py | 11 ++---
tools/perf/scripts/python/sched-migration.py | 14 ++++---
tools/perf/scripts/python/stat-cpi.py | 5 ++-
tools/perf/tests/attr.py | 32 +++++++++------
.../scripting-engines/trace-event-python.c | 29 +++++++-------
8 files changed, 74 insertions(+), 63 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-08 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 21:27 Jeremy Cline [this message]
2018-06-28 14:44 ` Arnaldo Carvalho de Melo
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=0100016341a7217a-d48a8d8a-c7ed-4857-82ef-9e2e599364e2-000000@email.amazonses.com \
--to=jeremy@jcline.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=herton@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--subject='Re: [PATCH 0/8] Improve Python 3 support in perf' \
/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
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).