From: Robin Murphy <robin.murphy@arm.com>
To: Jing Zhang <renyu.zj@linux.alibaba.com>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org,
Shuai Xue <xueshuai@linux.alibaba.com>,
Zhuo Song <zhuo.song@linux.alibaba.com>,
Ruidong Tian <tianruidong@linux.alibaba.com>
Subject: Re: [PATCH] perf/arm-cmn: fix regitster offset of CMN_MXP__CONNECT_INFO_P2-5
Date: Thu, 30 Mar 2023 11:34:22 +0100 [thread overview]
Message-ID: <3b95e362-300a-12af-0d55-76672c60be9f@arm.com> (raw)
In-Reply-To: <1680169620-26012-1-git-send-email-renyu.zj@linux.alibaba.com>
On 2023-03-30 10:47, Jing Zhang wrote:
> In the CMN700 specification, it is described that the address offset
> of the mxp_device_connect_info_p0-5 register is 16'h8 + #{8*index}.
> Therefore, the address offset of the CMN_MXP__CONNECT_INFO_P2-5 macro
> defined in the code is wrong, which causes the cmn700 topology map
> incorrect printed in debugfs.
>
> So correct the address offset value to make the cmn700 topology map
> correct in debugfs.
>
> Fixes: 60d1504070c2 ("perf/arm-cmn: Support new IP features")
Ugh, these offsets are correct for CI-700, so strictly that commit is
fine. What I failed to notice is that CMN-700 shuffled the
mesh_port_connect_info registers out of the way, so it's commit
23760a014417 which should have added more handling for this difference.
Thanks,
Robin.
> Signed-off-by: Jing Zhang <renyu.zj@linux.alibaba.com>
> Signed-off-by: Ruidong Tian <tianruidong@linux.alibaba.com>
> ---
> drivers/perf/arm-cmn.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/perf/arm-cmn.c b/drivers/perf/arm-cmn.c
> index 1deb61b..e9f844b 100644
> --- a/drivers/perf/arm-cmn.c
> +++ b/drivers/perf/arm-cmn.c
> @@ -59,10 +59,10 @@
> /* XPs also have some local topology info which has uses too */
> #define CMN_MXP__CONNECT_INFO_P0 0x0008
> #define CMN_MXP__CONNECT_INFO_P1 0x0010
> -#define CMN_MXP__CONNECT_INFO_P2 0x0028
> -#define CMN_MXP__CONNECT_INFO_P3 0x0030
> -#define CMN_MXP__CONNECT_INFO_P4 0x0038
> -#define CMN_MXP__CONNECT_INFO_P5 0x0040
> +#define CMN_MXP__CONNECT_INFO_P2 0x0018
> +#define CMN_MXP__CONNECT_INFO_P3 0x0020
> +#define CMN_MXP__CONNECT_INFO_P4 0x0028
> +#define CMN_MXP__CONNECT_INFO_P5 0x0030
> #define CMN__CONNECT_INFO_DEVICE_TYPE GENMASK_ULL(4, 0)
>
> /* PMU registers occupy the 3rd 4KB page of each node's region */
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-30 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 9:47 [PATCH] perf/arm-cmn: fix regitster offset of CMN_MXP__CONNECT_INFO_P2-5 Jing Zhang
2023-03-30 10:34 ` Robin Murphy [this message]
2023-04-03 7:45 ` Mark Rutland
2023-04-03 9:40 ` Robin Murphy
2023-04-03 9:42 ` Jing Zhang
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=3b95e362-300a-12af-0d55-76672c60be9f@arm.com \
--to=robin.murphy@arm.com \
--cc=ilkka@os.amperecomputing.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=renyu.zj@linux.alibaba.com \
--cc=tianruidong@linux.alibaba.com \
--cc=will@kernel.org \
--cc=xueshuai@linux.alibaba.com \
--cc=zhuo.song@linux.alibaba.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