From: Ingo Molnar <mingo@kernel.org>
To: Luo Gengkun <luogengkun@huaweicloud.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, tglx@linutronix.de, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
ravi.bangoria@amd.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/x86: Fix open counting event error
Date: Thu, 24 Apr 2025 18:20:17 +0200 [thread overview]
Message-ID: <aApkwfEUCJcc9PXn@gmail.com> (raw)
In-Reply-To: <20250423064724.3716211-1-luogengkun@huaweicloud.com>
* Luo Gengkun <luogengkun@huaweicloud.com> wrote:
> Perf doesn't work at perf stat for hardware events:
>
> $perf stat -- sleep 1
> Performance counter stats for 'sleep 1':
> 16.44 msec task-clock # 0.016 CPUs utilized
> 2 context-switches # 121.691 /sec
> 0 cpu-migrations # 0.000 /sec
> 54 page-faults # 3.286 K/sec
> <not supported> cycles
> <not supported> instructions
> <not supported> branches
> <not supported> branch-misses
>
> The reason is that the check in x86_pmu_hw_config for sampling event is
> unexpectedly applied to the counting event.
>
> Fixes: 88ec7eedbbd2 ("perf/x86: Fix low freqency setting issue")
> Signed-off-by: Luo Gengkun <luogengkun@huaweicloud.com>
> ---
> arch/x86/events/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
> index 6866cc5acb0b..3a4f031d2f44 100644
> --- a/arch/x86/events/core.c
> +++ b/arch/x86/events/core.c
> @@ -629,7 +629,7 @@ int x86_pmu_hw_config(struct perf_event *event)
> if (event->attr.type == event->pmu->type)
> event->hw.config |= x86_pmu_get_event_config(event);
>
> - if (!event->attr.freq && x86_pmu.limit_period) {
> + if (is_sampling_event(event) && !event->attr.freq && x86_pmu.limit_period) {
Hm, so how come it works here, on an affected x86 system:
$ perf stat -- sleep 1
Performance counter stats for 'sleep 1':
0.64 msec task-clock:u # 0.001 CPUs utilized
0 context-switches:u # 0.000 /sec
0 cpu-migrations:u # 0.000 /sec
73 page-faults:u # 114.063 K/sec
325,849 instructions:u # 0.56 insn per cycle
# 0.88 stalled cycles per insn
580,323 cycles:u # 0.907 GHz
286,348 stalled-cycles-frontend:u # 49.34% frontend cycles idle
72,623 branches:u # 113.474 M/sec
4,713 branch-misses:u # 6.49% of all branches
?
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-24 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 6:47 [PATCH] perf/x86: Fix open counting event error Luo Gengkun
2025-04-23 13:51 ` Liang, Kan
2025-04-24 6:52 ` Ravi Bangoria
2025-04-24 17:15 ` Liang, Kan
2025-04-25 10:12 ` Ravi Bangoria
2025-04-30 14:12 ` Liang, Kan
2025-04-24 16:20 ` Ingo Molnar [this message]
2025-04-24 17:08 ` Liang, Kan
2025-04-24 18:14 ` Ingo Molnar
2025-04-24 18:22 ` [tip: perf/urgent] perf/x86: Fix non-sampling (counting) events on certain x86 platforms tip-bot2 for Luo Gengkun
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=aApkwfEUCJcc9PXn@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=luogengkun@huaweicloud.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@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