From: Robin Murphy <robin.murphy@arm.com>
To: Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, patches@amperecomputing.com
Subject: Re: [PATCH 1/1] perf/arm-cmn: Add more bits to child node address offset field
Date: Tue, 9 Aug 2022 11:05:39 +0100 [thread overview]
Message-ID: <f2ccc321-c892-0e35-3760-1d0ed5b5dbf3@arm.com> (raw)
In-Reply-To: <20220808195455.79277-1-ilkka@os.amperecomputing.com>
On 2022-08-08 20:54, Ilkka Koskinen wrote:
> CMN-600 uses bits [27:0] for child node address offset while bits [30:28]
> are required to be zero.
>
> For CMN-650, the child node address offset field has been increased
> to include bits [29:0] while leaving only bit 30 set to zero.
>
> Let's include the missing two bits and assume older implementations
> comply with the spec and set bits [29:28] to 0.
Ah, I don't think it ever even crossed my mind to look for changes here,
but of course if the node regions have grown from 16KB to 64KB then it's
only natural that offsets grow to match. I expect the CMN-700 config
that we tested on internally would have been small enough for this not
to make a difference. Thanks for the catch!
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> Signed-off-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
> ---
>
> I have tested this patch on CMN-600 and CMN-650.
>
> drivers/perf/arm-cmn.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/perf/arm-cmn.c b/drivers/perf/arm-cmn.c
> index 80d8309652a4..b80a9b74662b 100644
> --- a/drivers/perf/arm-cmn.c
> +++ b/drivers/perf/arm-cmn.c
> @@ -36,7 +36,7 @@
> #define CMN_CI_CHILD_COUNT GENMASK_ULL(15, 0)
> #define CMN_CI_CHILD_PTR_OFFSET GENMASK_ULL(31, 16)
>
> -#define CMN_CHILD_NODE_ADDR GENMASK(27, 0)
> +#define CMN_CHILD_NODE_ADDR GENMASK(29, 0)
> #define CMN_CHILD_NODE_EXTERNAL BIT(31)
>
> #define CMN_MAX_DIMENSION 12
next prev parent reply other threads:[~2022-08-09 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 19:54 Ilkka Koskinen
2022-08-09 10:05 ` Robin Murphy [this message]
2022-08-31 4:46 ` Ilkka Koskinen
2022-09-21 16:17 ` Robin Murphy
2022-09-21 19:56 ` Ilkka Koskinen
2022-09-22 20:33 ` Will Deacon
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=f2ccc321-c892-0e35-3760-1d0ed5b5dbf3@arm.com \
--to=robin.murphy@arm.com \
--cc=ilkka@os.amperecomputing.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=patches@amperecomputing.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®