From: Ingo Molnar <mingo@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/4] perf stat: Allow no events to open if this is a "--null" run
Date: Tue, 2 Dec 2025 05:38:30 +0100 [thread overview]
Message-ID: <aS5tRnf801Sm3z8P@gmail.com> (raw)
In-Reply-To: <20251201230904.290733-1-irogers@google.com>
* Ian Rogers <irogers@google.com> wrote:
> It is intended that a "--null" run doesn't open any events.
>
> Fixes: 2cc7aa995ce9 ("perf stat: Refactor retry/skip/fatal error handling")
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/builtin-stat.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index 5c06e9b61821..6410115ed9c5 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -923,7 +923,7 @@ static int __run_perf_stat(int argc, const char **argv, int run_idx)
> goto err_out;
> }
> }
> - if (!has_supported_counters) {
> + if (!has_supported_counters && !stat_config.null_run) {
> evsel__open_strerror(evlist__first(evsel_list), &target, open_err,
> msg, sizeof(msg));
> ui__error("No supported events found.\n%s\n", msg);
Note that without the cpumask workaround patch I sent
'perf stat --null' still segfaults on perf-tools-next
even with the above patch applied - I suppose that's
expected, right?
Other than that:
Tested-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
next prev parent reply other threads:[~2025-12-02 4:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 23:09 [PATCH v1 1/4] perf stat: Allow no events to open if this is a "--null" run Ian Rogers
2025-12-01 23:09 ` [PATCH v1 2/4] libperf cpumap: Fix perf_cpu_map__max for an empty/NULL map Ian Rogers
2025-12-01 23:09 ` [PATCH v1 3/4] perf cpumap: Add "any" CPU handling to cpu_map__snprint_mask Ian Rogers
2025-12-01 23:09 ` [PATCH v1 4/4] perf tests stat: Add "--null" coverage Ian Rogers
2025-12-02 4:38 ` Ingo Molnar [this message]
2025-12-02 4:41 ` [PATCH v1 1/4] perf stat: Allow no events to open if this is a "--null" run Ingo Molnar
2025-12-02 4:45 ` Ingo Molnar
2025-12-02 4:52 ` Ingo Molnar
2025-12-03 21:49 ` Ian Rogers
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=aS5tRnf801Sm3z8P@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.