From: Pu Hu <hupu@transsion.com>
To: "peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"acme@kernel.org" <acme@kernel.org>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"irogers@google.com" <irogers@google.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"james.clark@linaro.org" <james.clark@linaro.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jiazi Li <jiazi.li@transsion.com>
Subject: Re: [RFC] perf pmu-events: Fix typo in idle-cycles-frontend description
Date: Sun, 2 Aug 2026 13:28:55 +0000 [thread overview]
Message-ID: <ca99c06e-a291-4c01-9b52-1308c6e33e64@transsion.com> (raw)
In-Reply-To: <20260802132536.4635-1-hupu@transsion.com>
On 8/2/2026 9:25 PM, Pu Hu wrote:
> From: Pu Hu <hupu@transsion.com>
>
> The brief description of the idle-cycles-frontend legacy hardware event
> refers to its alias as "stalled-cycles-fronted", but there is no such
> event. The correct event name is "stalled-cycles-frontend".
>
> This typo is visible in the output of "perf list", for example:
>
> idle-cycles-frontend
> [Stalled cycles during issue [This event is an alias of
> stalled-cycles-fronted]. Unit: armv8_pmuv3]
>
> Fix the spelling so that the description points to the valid event name.
>
> Signed-off-by: Pu Hu <hupu@transsion.com>
Hi maintainers,
Just to add some context, I reproduced this issue on an arm64 platform.
Without this patch, "perf list" reports:
idle-cycles-frontend
[Stalled cycles during issue [This event is an alias of
stalled-cycles-fronted]. Unit: armv8_pmuv3]
But there is no "stalled-cycles-fronted" event. The intended event name
is "stalled-cycles-frontend".
After the fix, the description points to the correct event name.
Thanks,
Pu Hu
next prev parent reply other threads:[~2026-08-02 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 13:25 Pu Hu
2026-08-02 13:28 ` Pu Hu [this message]
2026-08-04 17:04 ` Namhyung Kim
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=ca99c06e-a291-4c01-9b52-1308c6e33e64@transsion.com \
--to=hupu@transsion.com \
--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=jiazi.li@transsion.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®