public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Seongsu Park" <sgsu.park@samsung.com>
To: <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>, <infinite.run@gmail.com>,
	<sgsu.park@samsung.com>
Subject: RE: [PATCH] arm64: Cleanup __cpu_set_tcr_t0sz()
Date: Mon, 3 Jun 2024 20:02:52 +0900	[thread overview]
Message-ID: <000001dab5a5$94580a40$bd081ec0$@samsung.com> (raw)
In-Reply-To: <20240523122146.144483-1-sgsu.park@samsung.com>

Dear All,

Please check this patch.
I think this patch is appropriate.

Thanks.
Seongsu Park.

> -----Original Message-----
> From: Seongsu Park <sgsu.park@samsung.com>
> Sent: Thursday, May 23, 2024 9:22 PM
> To: 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;
> infinite.run@gmail.com; sgsu.park@samsung.com
> Subject: [PATCH] arm64: Cleanup __cpu_set_tcr_t0sz()
> 
> The T0SZ field of TCR_EL1 occupies bits 0-5 of the register and encode the
> virtual address space translated by TTBR0_EL1. When updating the field,
> for example because we are switching to/from the idmap page-table,
> __cpu_set_tcr_t0sz() erroneously treats its 't0sz' argument as unshifted,
> resulting in harmless but confusing double shifts by 0 in the code.
> 
> Co-developed-by: Leem ChaeHoon <infinite.run@gmail.com>
> Signed-off-by: Leem ChaeHoon <infinite.run@gmail.com>
> Signed-off-by: Seongsu Park <sgsu.park@samsung.com>
> ---
>  arch/arm64/include/asm/mmu_context.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/include/asm/mmu_context.h
> b/arch/arm64/include/asm/mmu_context.h
> index c768d16b81a4..bd19f4c758b7 100644
> --- a/arch/arm64/include/asm/mmu_context.h
> +++ b/arch/arm64/include/asm/mmu_context.h
> @@ -72,11 +72,11 @@ static inline void __cpu_set_tcr_t0sz(unsigned long
> t0sz)  {
>  	unsigned long tcr = read_sysreg(tcr_el1);
> 
> -	if ((tcr & TCR_T0SZ_MASK) >> TCR_T0SZ_OFFSET == t0sz)
> +	if ((tcr & TCR_T0SZ_MASK) == t0sz)
>  		return;
> 
>  	tcr &= ~TCR_T0SZ_MASK;
> -	tcr |= t0sz << TCR_T0SZ_OFFSET;
> +	tcr |= t0sz;
>  	write_sysreg(tcr, tcr_el1);
>  	isb();
>  }
> --
> 2.34.1



  reply	other threads:[~2024-06-03 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240523122152epcas1p49d579e40d4ef0c442820cc01f79ab38b@epcas1p4.samsung.com>
2024-05-23 12:21 ` [PATCH] arm64: Cleanup __cpu_set_tcr_t0sz() Seongsu Park
2024-06-03 11:02   ` Seongsu Park [this message]
2024-06-24 12:37   ` Seongsu Park
2024-06-24 18:12   ` Catalin Marinas

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='000001dab5a5$94580a40$bd081ec0$@samsung.com' \
    --to=sgsu.park@samsung.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=infinite.run@gmail.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