From: Adrian Hunter <adrian.hunter@intel.com>
To: Alexander Pantyukhin <apantykhin@gmail.com>,
peterz@infradead.org, akpm@linux-foundation.org
Cc: mingo@redhat.com, namhyung@kernel.org, jolsa@kernel.org,
acme@kernel.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools:perf:scripts:python:intel-pt-events del unusedvar
Date: Sat, 14 Jan 2023 09:24:03 +0200 [thread overview]
Message-ID: <a6a2e8b1-7194-75f1-d59c-7c8bc059174a@intel.com> (raw)
In-Reply-To: <20230106215613.7159-1-apantykhin@gmail.com>
On 6/01/23 23:56, Alexander Pantyukhin wrote:
> The event_attr is never used later, the var is ok be deleted.
> Additional code simplification is to substitute string slice comparison
> with "substring" function. This case no need to know the length specific
> words.
>
> Signed-off-by: Alexander Pantyukhin <apantykhin@gmail.com>
> ---
> tools/perf/scripts/python/intel-pt-events.py | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/scripts/python/intel-pt-events.py b/tools/perf/scripts/python/intel-pt-events.py
> index 08862a2582f4..28d08e2fb7cd 100644
> --- a/tools/perf/scripts/python/intel-pt-events.py
> +++ b/tools/perf/scripts/python/intel-pt-events.py
> @@ -340,7 +340,6 @@ def print_srccode(comm, param_dict, sample, symbol, dso, with_insn):
> print(start_str, src_str)
>
> def do_process_event(param_dict):
> - event_attr = param_dict["attr"]
Should really be moved to the "Unused fields:" comment
section a few lines below.
> sample = param_dict["sample"]
> raw_buf = param_dict["raw_buf"]
> comm = param_dict["comm"]
> @@ -359,13 +358,13 @@ def do_process_event(param_dict):
> print(glb_switch_str[cpu])
> del glb_switch_str[cpu]
>
> - if name[0:12] == "instructions":
> + if name.startswith("instructions"):
> if glb_src:
> print_srccode(comm, param_dict, sample, symbol, dso, True)
> else:
> print_instructions_start(comm, sample)
> print_common_ip(param_dict, sample, symbol, dso)
> - elif name[0:8] == "branches":
> + elif name.startswith("branches"):
> if glb_src:
> print_srccode(comm, param_dict, sample, symbol, dso, False)
> else:
next prev parent reply other threads:[~2023-01-14 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 21:56 [PATCH] tools:perf:scripts:python:intel-pt-events del unusedvar Alexander Pantyukhin
2023-01-14 7:24 ` Adrian Hunter [this message]
2023-01-14 13:10 ` Alexander Pantyukhin
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=a6a2e8b1-7194-75f1-d59c-7c8bc059174a@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apantykhin@gmail.com \
--cc=jolsa@kernel.org \
--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 \
/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).