From: Jens Remus <jremus@linux.ibm.com>
To: Jan Polensky <japo@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-s390@vger.kernel.org, Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v2] perf evsel: Improve callchain warning for s390
Date: Fri, 21 Aug 2026 15:03:18 +0200 [thread overview]
Message-ID: <ba75c436-ae41-4754-8a73-80e2e5df76e7@linux.ibm.com> (raw)
In-Reply-To: <20260821125538.3721169-1-jremus@linux.ibm.com>
On 8/21/2026 2:55 PM, Jens Remus wrote:
> Instead, warn on s390 when callchain sampling is requested with an event
> provided by the CPUMSF hardware PMU, because that combination is not
> supported.
> diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
> @@ -1078,9 +1078,8 @@ static void __evsel__config_callchain(struct evsel *evsel, const struct record_o
> bool function = evsel__is_function_event(evsel);
> struct perf_event_attr *attr = &evsel->core.attr;
>
> - if (EM_HOST == EM_S390 && param->record_mode == CALLCHAIN_FP) {
> - pr_warning_once(
> - "Framepointer unwinding lacks kernel support. Use '--call-graph dwarf'\n");
> + if (EM_HOST == EM_S390 && evsel->pmu && !perf_pmu__is_software(evsel->pmu)) {
> + pr_warning_once("Cannot use hardware CPUMSF event with -g and --call-graph.\n");
Jan, Thomas, could you please do me a favor and test whether this works
as expected on LPAR with CPUMSF? Time was running out before I leave on
vacation.
> }
>
> evsel__set_sample_bit(evsel, CALLCHAIN);
Thanks and regards,
Jens
--
Jens Remus
Linux on Z Development (D3303)
jremus@de.ibm.com / jremus@linux.ibm.com
IBM Deutschland Research & Development GmbH; Vorsitzender des Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der Gesellschaft: Ehningen; Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM Data Privacy Statement: https://www.ibm.com/privacy/
prev parent reply other threads:[~2026-08-21 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 12:55 [PATCH v2] perf evsel: Improve callchain warning for s390 Jens Remus
2026-08-21 13:03 ` Jens Remus [this message]
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=ba75c436-ae41-4754-8a73-80e2e5df76e7@linux.ibm.com \
--to=jremus@linux.ibm.com \
--cc=acme@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=irogers@google.com \
--cc=japo@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=tmricht@linux.ibm.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