From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [boot-wrapper 3/3] aarch64: Enable access into RCW[S]MASK_EL1 registers from EL2 and below
Date: Fri, 26 Jul 2024 14:01:49 +0530 [thread overview]
Message-ID: <85e9b2ce-775a-4183-91e3-65b8eec0bdad@arm.com> (raw)
In-Reply-To: <ZqIR9SBBDf4kfGto@J2N7QTR9R3>
On 7/25/24 14:21, Mark Rutland wrote:
> On Tue, Jul 23, 2024 at 04:36:30PM +0530, Anshuman Khandual wrote:
>> FEAT_THE adds RCW[S]MASK_EL1 system registers. But access into these system
>> registers from EL2 and below trap to EL3 unless SCR_EL3.RCWMASKEn is set.
>>
>> Enable access to RCW[S]MASK_EL1 registers when they are implemented.
>
> This looks fine.
>
> IIUC we don't need to initialize these new registers as they only affect
> the behaviour of new instructions which we don't expect SW to use until
> privileged SW has configured these registers (as they reset to UNKNOWN
> values even at the highest implemented EL).
Right, will keep patch's position in the series unchanged as well.
>
> Mark.
>
>> 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 57d66e4..8404152 100644
>> --- a/arch/aarch64/include/asm/cpu.h
>> +++ b/arch/aarch64/include/asm/cpu.h
>> @@ -55,6 +55,7 @@
>> #define SCR_EL3_TME BIT(34)
>> #define SCR_EL3_HXEn BIT(38)
>> #define SCR_EL3_EnTP2 BIT(41)
>> +#define SCR_EL3_RCWMASKEn BIT(42)
>> #define SCR_EL3_TCR2EN BIT(43)
>> #define SCR_EL3_SCTLR2En BIT(44)
>> #define SCR_EL3_PIEN BIT(45)
>> @@ -92,6 +93,7 @@
>>
>> #define ID_AA64PFR1_EL1_MTE BITS(11, 8)
>> #define ID_AA64PFR1_EL1_SME BITS(27, 24)
>> +#define ID_AA64PFR1_EL1_THE BITS(51, 48)
>> #define ID_AA64PFR0_EL1_SVE BITS(35, 32)
>>
>> #define ID_AA64SMFR0_EL1 s3_0_c0_c4_5
>> diff --git a/arch/aarch64/init.c b/arch/aarch64/init.c
>> index 5b21cb8..13a2339 100644
>> --- a/arch/aarch64/init.c
>> +++ b/arch/aarch64/init.c
>> @@ -95,6 +95,9 @@ void cpu_init_el3(void)
>> if (mrs_field(ID_AA64MMFR3_EL1, SCTLRX))
>> scr |= SCR_EL3_SCTLR2En;
>>
>> + if (mrs_field(ID_AA64PFR1_EL1, THE))
>> + scr |= SCR_EL3_RCWMASKEn;
>> +
>> msr(SCR_EL3, scr);
>>
>> msr(CPTR_EL3, cptr);
>> --
>> 2.25.1
>>
prev parent reply other threads:[~2024-07-26 8:32 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
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 [this message]
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=85e9b2ce-775a-4183-91e3-65b8eec0bdad@arm.com \
--to=anshuman.khandual@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.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