From: Chun-Tse Shao <ctshao@google.com>
To: acme@kernel.org, namhyung@kernel.org
Cc: irogers@google.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, Chun-Tse Shao <ctshao@google.com>
Subject: [PATCH] perf stat: Fix false NMI watchdog warning in aggregation modes
Date: Wed, 10 Jun 2026 10:35:01 -0700 [thread overview]
Message-ID: <20260610173501.3557522-1-ctshao@google.com> (raw)
In aggregation modes (e.g. --per-socket, --per-die, etc.), a
counter might not be scheduled or counted on specific aggregate
groups if it was not assigned to the CPUs belonging to those
groups. However, the printout() check triggers the
"print_free_counters_hint" logic unconditionally for any
supported counter with a missing count. This results in a false
"Some events weren't counted. Try disabling the NMI watchdog"
warning.
This warning was originally introduced in commit 02d492e5dcb7
("perf stat: Issue a HW watchdog disable hint").
To fix this, add the helper evsel__should_run_on_aggr() to
verify if the counter was supposed to run on the aggregate CPU
ID before triggering the hint. Additionally, correctly handle
per-thread/per-process execution (which uses a dummy CPU map
with a single -1 entry) by immediately returning true,
ensuring legitimate warnings are still reported.
Example before/after:
$ perf stat -M lpm_miss_lat --metric-only --per-socket -a -- sleep 1
Before:
Performance counter stats for 'system wide':
ns lpm_miss_lat_rem ns lpm_miss_lat_loc
S0 126 202.3 207.9
S1 126 231.9 259.3
1.006029831 seconds time elapsed
Some events weren't counted. Try disabling the NMI watchdog:
echo 0 > /proc/sys/kernel/nmi_watchdog
perf stat ...
echo 1 > /proc/sys/kernel/nmi_watchdog
After:
Performance counter stats for 'system wide':
ns lpm_miss_lat_rem ns lpm_miss_lat_loc
S0 126 202.3 207.9
S1 126 231.9 259.3
1.006029831 seconds time elapsed
Assisted-by: Gemini:gemini-next
Signed-off-by: Chun-Tse Shao <ctshao@google.com>
---
tools/perf/util/stat-display.c | 25 ++++++++++++++++++++++++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/stat-display.c b/tools/perf/util/stat-display.c
index 2b69d238858c..e50557964916 100644
--- a/tools/perf/util/stat-display.c
+++ b/tools/perf/util/stat-display.c
@@ -792,6 +792,28 @@ static bool evlist__has_hybrid_pmus(struct evlist *evlist)
return false;
}
+static bool evsel__should_run_on_aggr(struct perf_stat_config *config,
+ struct evsel *counter,
+ const struct aggr_cpu_id *id)
+{
+ struct perf_cpu cpu;
+ unsigned int idx;
+
+ if (!config->aggr_map || !config->aggr_get_id)
+ return true;
+
+ perf_cpu_map__for_each_cpu(cpu, idx, counter->core.cpus) {
+ struct aggr_cpu_id own_id;
+
+ if (cpu.cpu < 0)
+ return true;
+
+ own_id = config->aggr_get_id(config, cpu);
+ if (aggr_cpu_id__equal(id, &own_id))
+ return true;
+ }
+ return false;
+}
static void printout(struct perf_stat_config *config, struct outstate *os,
double uval, u64 run, u64 ena, double noise, int aggr_idx)
{
@@ -822,7 +844,8 @@ static void printout(struct perf_stat_config *config, struct outstate *os,
if (counter->supported) {
if (!evlist__has_hybrid_pmus(counter->evlist)) {
- config->print_free_counters_hint = 1;
+ if (evsel__should_run_on_aggr(config, counter, &os->id))
+ config->print_free_counters_hint = 1;
}
}
}
--
2.54.0.1099.g489fc7bff1-goog
next reply other threads:[~2026-06-10 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 17:35 Chun-Tse Shao [this message]
2026-06-11 22:07 ` [PATCH] perf stat: Fix false NMI watchdog warning in aggregation modes Chun-Tse Shao
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=20260610173501.3557522-1-ctshao@google.com \
--to=ctshao@google.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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