From: Mark Rutland <mark.rutland@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [boot-wrapper 1/3] aarch64: Enable access into 128 bit system registers from EL2 and below
Date: Thu, 25 Jul 2024 09:44:05 +0100 [thread overview]
Message-ID: <ZqIQVSOYQtVR4OLN@J2N7QTR9R3> (raw)
In-Reply-To: <20240723110630.483871-2-anshuman.khandual@arm.com>
On Tue, Jul 23, 2024 at 04:36:28PM +0530, Anshuman Khandual wrote:
> FEAT_D128 adds 128 bit system registers like PAR_EL1, TTBR0_EL1, TTBR1_EL1,
> TTBR0_EL2, TTBR1_EL2, TTBR0_EL12, TTBR1_EL12 , VTTBR_EL2, RCWMASK_EL1, and
> RCWSMASK_EL1. But access into these register from EL2 and below trap to EL3
> unless SCR_EL3.D128En is set.
Do we need to initialize any of these new bits, or do they have no
effect on a lower EL unless explicitly opted-in at that lower EL?
Otherwise this looks superficially fine, but it should come after
enabling SCTLR2.
Mark.
>
> Enable access to 128 bit registers when they are implemented.
>
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
> arch/aarch64/include/asm/cpu.h | 2 ++
> arch/aarch64/init.c | 3 +++
> 2 files changed, 5 insertions(+)
>
> diff --git a/arch/aarch64/include/asm/cpu.h b/arch/aarch64/include/asm/cpu.h
> index 124ef91..0b8b463 100644
> --- a/arch/aarch64/include/asm/cpu.h
> +++ b/arch/aarch64/include/asm/cpu.h
> @@ -57,6 +57,7 @@
> #define SCR_EL3_EnTP2 BIT(41)
> #define SCR_EL3_TCR2EN BIT(43)
> #define SCR_EL3_PIEN BIT(45)
> +#define SCR_EL3_D128En BIT(47)
>
> #define HCR_EL2_RES1 BIT(1)
>
> @@ -85,6 +86,7 @@
> #define ID_AA64MMFR3_EL1_S2PIE BITS(15, 12)
> #define ID_AA64MMFR3_EL1_S1POE BITS(19, 16)
> #define ID_AA64MMFR3_EL1_S2POE BITS(23, 20)
> +#define ID_AA64MMFR3_EL1_D128 BITS(35, 32)
>
> #define ID_AA64PFR1_EL1_MTE BITS(11, 8)
> #define ID_AA64PFR1_EL1_SME BITS(27, 24)
> diff --git a/arch/aarch64/init.c b/arch/aarch64/init.c
> index 37cb45f..7d9d0d9 100644
> --- a/arch/aarch64/init.c
> +++ b/arch/aarch64/init.c
> @@ -89,6 +89,9 @@ void cpu_init_el3(void)
> if (!kernel_is_32bit())
> scr |= SCR_EL3_RW;
>
> + if (mrs_field(ID_AA64MMFR3_EL1, D128))
> + scr |= SCR_EL3_D128En;
> +
> msr(SCR_EL3, scr);
>
> msr(CPTR_EL3, cptr);
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-07-25 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 11:06 [boot-wrapper 0/3] aarch64: Enable access for FEAT_D128 registers in EL1/EL2 Anshuman Khandual
2024-07-23 11:06 ` [boot-wrapper 1/3] aarch64: Enable access into 128 bit system registers from EL2 and below Anshuman Khandual
2024-07-25 8:44 ` Mark Rutland [this message]
2024-07-26 7:12 ` Anshuman Khandual
2024-07-23 11:06 ` [boot-wrapper 2/3] aarch64: Enable access into SCTLR2_ELx " Anshuman Khandual
2024-07-25 8:40 ` Mark Rutland
2024-07-26 6:55 ` Anshuman Khandual
2024-07-26 8:45 ` Mark Rutland
2024-07-23 11:06 ` [boot-wrapper 3/3] aarch64: Enable access into RCW[S]MASK_EL1 " Anshuman Khandual
2024-07-25 8:51 ` Mark Rutland
2024-07-26 8:31 ` Anshuman Khandual
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=ZqIQVSOYQtVR4OLN@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=linux-arm-kernel@lists.infradead.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