From: Robin Murphy <robin.murphy@arm.com>
To: Seongsu Park <sgsu.park@samsung.com>,
catalin.marinas@arm.com, will@kernel.org, ardb@kernel.org,
mark.rutland@arm.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Leem ChaeHoon <infinite.run@gamil.com>,
Gyeonggeon Choi <gychoi@student.42seoul.kr>,
Soomin Cho <to.soomin@gmail.com>, DaeRo Lee <skseofh@gmail.com>,
kmasta <kmasta.study@gmail.com>
Subject: Re: [PATCH] arm64: Fix double TCR_T0SZ_OFFSET shift
Date: Fri, 5 Apr 2024 15:10:41 +0100 [thread overview]
Message-ID: <94af4af9-8cef-4673-bce5-16bd5edb28dd@arm.com> (raw)
In-Reply-To: <20240402104735.170539-1-sgsu.park@samsung.com>
On 2024-04-02 11:47 am, Seongsu Park wrote:
> We have already shifted the value of t0sz in TCR_T0SZ by TCR_T0SZ_OFFSET.
> So, the TCR_T0SZ_OFFSET shift here should be removed.
If the shift for assigning the t0sz value to the TCR field is wrong,
then the other shift for comparing the same t0sz value to the existing
TCR field must also be wrong. Really, this many people involved in
writing a patch and still nobody spotted the obvious?
Thanks,
Robin.
> Co-developed-by: Leem ChaeHoon <infinite.run@gamil.com>
> Signed-off-by: Leem ChaeHoon <infinite.run@gamil.com>
> Co-developed-by: Gyeonggeon Choi <gychoi@student.42seoul.kr>
> Signed-off-by: Gyeonggeon Choi <gychoi@student.42seoul.kr>
> Co-developed-by: Soomin Cho <to.soomin@gmail.com>
> Signed-off-by: Soomin Cho <to.soomin@gmail.com>
> Co-developed-by: DaeRo Lee <skseofh@gmail.com>
> Signed-off-by: DaeRo Lee <skseofh@gmail.com>
> Co-developed-by: kmasta <kmasta.study@gmail.com>
> Signed-off-by: kmasta <kmasta.study@gmail.com>
> Signed-off-by: Seongsu Park <sgsu.park@samsung.com>
> ---
> arch/arm64/include/asm/mmu_context.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/include/asm/mmu_context.h b/arch/arm64/include/asm/mmu_context.h
> index c768d16b81a4..58de99836d2e 100644
> --- a/arch/arm64/include/asm/mmu_context.h
> +++ b/arch/arm64/include/asm/mmu_context.h
> @@ -76,7 +76,7 @@ static inline void __cpu_set_tcr_t0sz(unsigned long t0sz)
> return;
>
> tcr &= ~TCR_T0SZ_MASK;
> - tcr |= t0sz << TCR_T0SZ_OFFSET;
> + tcr |= t0sz;
> write_sysreg(tcr, tcr_el1);
> isb();
> }
_______________________________________________
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:[~2024-04-05 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240402104742epcas1p306e175348a3a7c1bdba9422ce22284f8@epcas1p3.samsung.com>
2024-04-02 10:47 ` [PATCH] arm64: Fix double TCR_T0SZ_OFFSET shift Seongsu Park
2024-04-05 14:10 ` Robin Murphy [this message]
[not found] <CGME20240402104955epcas1p3dd15334a1305b99f3e1b82000e3c7c42@epcas1p3.samsung.com>
2024-04-02 10:49 ` Seongsu Park
2024-04-02 11:58 ` Will Deacon
2024-04-03 2:08 ` Seongsu Park
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=94af4af9-8cef-4673-bce5-16bd5edb28dd@arm.com \
--to=robin.murphy@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gychoi@student.42seoul.kr \
--cc=infinite.run@gamil.com \
--cc=kmasta.study@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sgsu.park@samsung.com \
--cc=skseofh@gmail.com \
--cc=to.soomin@gmail.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