From: Andi Kleen <ak@linux.intel.com>
To: linux-perf-users@vger.kernel.org
Cc: Andi Kleen <ak@linux.intel.com>
Subject: [PATCH v6 3/4] perf script: Fix perf script -F +metric
Date: Tue, 23 Jul 2024 13:48:33 -0700 [thread overview]
Message-ID: <20240723204834.3617647-3-ak@linux.intel.com> (raw)
In-Reply-To: <20240723204834.3617647-1-ak@linux.intel.com>
This fixes a regression with perf script -F +metric originally caused by :
commit 37cc8ad77cf81f3ffd226856c367b0e15333a738
Author: Ian Rogers <irogers@google.com>
Date: Sun Feb 19 01:28:46 2023 -0800
perf metric: Directly use counts rather than saved_value
In the perf script environment the evsel wouldn't allocate an aggr
values array, which led to a -1 reference because the metric
evaluation would try to reference NULL - 1 (for aggr_idx)
Give the perf script evsels a single CPU aggr setup. That's
enough because the groups are always contiguous, so no need
to store more than one CPU's worth of values.
Before
% perf record -e '{cycles,instructions}:S' perf bench mem memcpy
% perf script -F +metric
Segmentation fault (core dumped)
After:
% perf record -e '{cycles,instructions}:S' perf bench mem memcpy
...
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.028 MB perf.data (90 samples) ]
% perf script -F +metric
perf-exec 1847557 264658.180789: 3009 cycles: ffffffff990a579a native_write_msr+0xa ([kernel.kallsyms])
perf-exec 1847557 264658.180789: 382 instructions: ffffffff990a579a native_write_msr+0xa ([kernel.kallsyms])
perf-exec 1847557 264658.180789: metric: 0.13 insn per cycle
...
Fixes: 37cc8ad77cf8 ("perf metric: Directly use counts rather ...")
Signed-off-by: Andi Kleen <ak@linux.intel.com>
----
v2: Reformat code
v3: Work around bogus warning
v4: Set up aggr map only for metrics case to keep perf stat record
working
v5: Broken version
v6: Only set up limited aggregation mode with -F +metric. Add conflict
checks with perf stat record files.
---
tools/perf/builtin-script.c | 33 ++++++++++++++++++++++++++++++++-
1 file changed, 32 insertions(+), 1 deletion(-)
diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
index c16224b1fef3..1a4b9b3d240d 100644
--- a/tools/perf/builtin-script.c
+++ b/tools/perf/builtin-script.c
@@ -2133,12 +2133,17 @@ static void perf_sample__fprint_metric(struct perf_script *script,
if (evsel_script(leader)->gnum++ == 0)
perf_stat__reset_shadow_stats();
val = sample->period * evsel->scale;
+ /*
+ * Always use CPU 0 storage because the groups are contiguous
+ * and there's no need to handle multiple indexes for anything
+ */
+ evsel->stats->aggr[0].counts.val = val;
evsel_script(evsel)->val = val;
if (evsel_script(leader)->gnum == leader->core.nr_members) {
for_each_group_member (ev2, leader) {
perf_stat__print_shadow_stats(&stat_config, ev2,
evsel_script(ev2)->val,
- sample->cpu,
+ 0,
&ctx,
NULL);
}
@@ -2325,6 +2330,20 @@ static void process_event(struct perf_script *script,
fflush(fp);
}
+static void check_metric_conflict(void)
+{
+ int i;
+ /*
+ * Avoid conflict with the aggregation mode used for the metric printing.
+ */
+ for (i = 0; i < OUTPUT_TYPE_MAX; i++) {
+ if (output[i].fields & PERF_OUTPUT_METRIC) {
+ fprintf(stderr, "perf stat record files are not supported with -F metric\n");
+ exit(1);
+ }
+ }
+}
+
static struct scripting_ops *scripting_ops;
static void __process_stat(struct evsel *counter, u64 tstamp)
@@ -2334,6 +2353,8 @@ static void __process_stat(struct evsel *counter, u64 tstamp)
struct perf_cpu cpu;
static int header_printed;
+ check_metric_conflict();
+
if (!header_printed) {
printf("%3s %8s %15s %15s %15s %15s %s\n",
"CPU", "THREAD", "VAL", "ENA", "RUN", "TIME", "EVENT");
@@ -3725,6 +3746,8 @@ static int process_stat_config_event(struct perf_session *session __maybe_unused
{
perf_event__read_stat_config(&stat_config, &event->stat_config);
+ check_metric_conflict();
+
/*
* Aggregation modes are not used since post-processing scripts are
* supposed to take care of such requirements
@@ -3760,6 +3783,8 @@ int process_thread_map_event(struct perf_session *session,
struct perf_tool *tool = session->tool;
struct perf_script *script = container_of(tool, struct perf_script, tool);
+ check_metric_conflict();
+
if (dump_trace)
perf_event__fprintf_thread_map(event, stdout);
@@ -3785,6 +3810,8 @@ int process_cpu_map_event(struct perf_session *session,
if (dump_trace)
perf_event__fprintf_cpu_map(event, stdout);
+ check_metric_conflict();
+
if (script->cpus) {
pr_warning("Extra cpu map event, ignoring.\n");
return 0;
@@ -4088,6 +4115,10 @@ int cmd_script(int argc, const char **argv)
argc = parse_options_subcommand(argc, argv, options, script_subcommands, script_usage,
PARSE_OPT_STOP_AT_NON_OPTION);
+ for (i = 0; i < OUTPUT_TYPE_MAX; i++) {
+ if (output[i].fields & PERF_OUTPUT_METRIC)
+ stat_config.aggr_map = &(struct cpu_aggr_map){ .nr = 1 };
+ }
if (symbol_conf.guestmount ||
symbol_conf.default_guest_vmlinux_name ||
--
2.45.2
next prev parent reply other threads:[~2024-07-23 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 20:48 [PATCH v6 1/4] Create source symlink in perf object dir Andi Kleen
2024-07-23 20:48 ` [PATCH v6 2/4] perf test: Support external tests for separate objdir Andi Kleen
2024-07-23 20:48 ` Andi Kleen [this message]
2024-07-23 21:32 ` [PATCH v6 3/4] perf script: Fix perf script -F +metric Ian Rogers
2024-07-23 23:29 ` Andi Kleen
2024-07-24 0:05 ` Ian Rogers
2024-07-24 0:36 ` Andi Kleen
2024-07-23 20:48 ` [PATCH v6 4/4] Add a test case for " Andi Kleen
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=20240723204834.3617647-3-ak@linux.intel.com \
--to=ak@linux.intel.com \
--cc=linux-perf-users@vger.kernel.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).