From: Robin Murphy <robin.murphy@arm.com>
To: Ba Jing <bajing@cmss.chinamobile.com>
Cc: will@kernel.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: arm-cmn: remove unused macro
Date: Mon, 14 Oct 2024 15:12:14 +0100 [thread overview]
Message-ID: <ce396f01-e10c-41ce-b3d8-19c626d68241@arm.com> (raw)
In-Reply-To: <20241012092411.2497-1-bajing@cmss.chinamobile.com>
On 12/10/2024 10:24 am, Ba Jing wrote:
> By reading the code, I found the marco CMN_HNP_PMU_EVENT_SEL
> is never referenced in the code. Just remove it.
Hmm, perhaps I got a little carried away implementing Mark's
recommendation in 88b63a82c84e ("perf/arm-cmn: Fix CCLA register
offset"), and the HN-P/CCLA_RNI case could have been left as it was
using CMN_HNP_PMU_EVENT_SEL. Either way, I think it's beneficial to keep
both definitions next to each other, so that it's at least visible from
the code alone (without having to resort to the CMN documentation) that
the two node types do have equivalent offsets and that combined case is
still not a bug.
Thanks,
Robin.
> Signed-off-by: Ba Jing <bajing@cmss.chinamobile.com>
> ---
> drivers/perf/arm-cmn.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/perf/arm-cmn.c b/drivers/perf/arm-cmn.c
> index 397a46410f7c..37b62d0dcc06 100644
> --- a/drivers/perf/arm-cmn.c
> +++ b/drivers/perf/arm-cmn.c
> @@ -79,7 +79,6 @@
>
> /* Some types are designed to coexist with another device in the same node */
> #define CMN_CCLA_PMU_EVENT_SEL 0x008
> -#define CMN_HNP_PMU_EVENT_SEL 0x008
>
> /* DTMs live in the PMU space of XP registers */
> #define CMN_DTM_WPn(n) (0x1A0 + (n) * 0x18)
prev parent reply other threads:[~2024-10-14 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 9:24 Ba Jing
2024-10-14 14:12 ` Robin Murphy [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=ce396f01-e10c-41ce-b3d8-19c626d68241@arm.com \
--to=robin.murphy@arm.com \
--cc=bajing@cmss.chinamobile.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@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
all inboxes | Powered by JetHome®