From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org,
Riccardo Mancini <rickyman7@gmail.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: [PATCH 2/3] perf script: Fix CPU filtering of a script's switch events
Date: Wed, 15 Dec 2021 10:06:35 +0200 [thread overview]
Message-ID: <20211215080636.149562-3-adrian.hunter@intel.com> (raw)
In-Reply-To: <20211215080636.149562-1-adrian.hunter@intel.com>
CPU filtering was not being applied to a script's switch events.
Fixes: 5bf83c29a0ad2 ("perf script: Add scripting operation process_switch()")
Cc: stable@vger.kernel.org
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
tools/perf/builtin-script.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
index 9434367af166..c82b033e8942 100644
--- a/tools/perf/builtin-script.c
+++ b/tools/perf/builtin-script.c
@@ -2473,7 +2473,7 @@ static int process_switch_event(struct perf_tool *tool,
if (perf_event__process_switch(tool, event, sample, machine) < 0)
return -1;
- if (scripting_ops && scripting_ops->process_switch)
+ if (scripting_ops && scripting_ops->process_switch && !filter_cpu(sample))
scripting_ops->process_switch(event, sample, machine);
if (!script->show_switch_events)
--
2.25.1
next prev parent reply other threads:[~2021-12-15 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 8:06 [PATCH 0/3] perf intel-pt: 3 more small fixes Adrian Hunter
2021-12-15 8:06 ` [PATCH 1/3] perf intel-pt: Fix parsing of VM time correlation arguments Adrian Hunter
2021-12-15 18:04 ` Namhyung Kim
2021-12-15 8:06 ` Adrian Hunter [this message]
2021-12-15 18:05 ` [PATCH 2/3] perf script: Fix CPU filtering of a script's switch events Namhyung Kim
2021-12-15 8:06 ` [PATCH 3/3] perf scripts python: intel-pt-events.py: Fix printing of " Adrian Hunter
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=20211215080636.149562-3-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=rickyman7@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).