* [PATCH v2 0/4] arm64: Support of PAuth QARMA3 architected algorithm
@ 2022-01-31 17:06 Vladimir Murzin
2022-01-31 17:06 ` [PATCH v2 1/4] arm64: cpufeature: Account min_field_value when cheking secondaries for PAuth Vladimir Murzin
` (5 more replies)
0 siblings, 6 replies; 16+ messages in thread
From: Vladimir Murzin @ 2022-01-31 17:06 UTC (permalink / raw)
To: linux-arm-kernel; +Cc: maz, catalin.marinas, mark.rutland, will
QARMA3 is relaxed version of the QARMA5 algorithm which expected to
reduce the latency of calculation while still delivering a suitable
level of security.
Feature advertised via a new ID fields in ID_AA64ISAR2_EL1 [1], so we
need to teach the kernel to identify this.
[1] https://developer.arm.com/documentation/ddi0601/2021-12/AArch64-Registers/ID-AA64ISAR2-EL1--AArch64-Instruction-Set-Attribute-Register-2?lang=en
Changelog:
v1 -> v2
- Removed unintended whitespace change in sysreg.h
- FTR_ALIAS_OPTION_LEN now accounts null terminator
- Extract only APA3 bits from ID_AA64ISAR2_APA3_SHIFT (in
contrast to id_aa64isar1_el1 where both APA and API bits
are extracted) in asm_pointer_auth.h
Thanks!
Vladimir Murzin (4):
arm64: cpufeature: Account min_field_value when cheking secondaries
for PAuth
arm64: cpufeature: Warn if mutually exclusive PAuth algorithms
detected
arm64: cpufeature: Mark existing PAuth architected algorithm as QARMA5
arm64: Add support of PAuth QARMA3 architected algorithm
arch/arm64/include/asm/asm_pointer_auth.h | 3 ++
arch/arm64/include/asm/cpufeature.h | 1 +
arch/arm64/include/asm/kvm_hyp.h | 1 +
arch/arm64/include/asm/sysreg.h | 12 +++++
arch/arm64/kernel/cpufeature.c | 63 ++++++++++++++++++++++----
arch/arm64/kernel/idreg-override.c | 16 ++++++-
arch/arm64/kvm/arm.c | 1 +
arch/arm64/kvm/hyp/include/nvhe/fixed_config.h | 5 ++
arch/arm64/kvm/hyp/nvhe/sys_regs.c | 14 ++++++
arch/arm64/kvm/sys_regs.c | 5 ++
arch/arm64/tools/cpucaps | 6 ++-
11 files changed, 114 insertions(+), 13 deletions(-)
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread* [PATCH v2 1/4] arm64: cpufeature: Account min_field_value when cheking secondaries for PAuth 2022-01-31 17:06 [PATCH v2 0/4] arm64: Support of PAuth QARMA3 architected algorithm Vladimir Murzin @ 2022-01-31 17:06 ` Vladimir Murzin 2022-02-04 18:13 ` Catalin Marinas 2022-01-31 17:06 ` [PATCH v2 2/4] arm64: cpufeature: Warn if mutually exclusive PAuth algorithms detected Vladimir Murzin ` (4 subsequent siblings) 5 siblings, 1 reply; 16+ messages in thread From: Vladimir Murzin @ 2022-01-31 17:06 UTC (permalink / raw) To: linux-arm-kernel; +Cc: maz, catalin.marinas, mark.rutland, will In case, both boot_val and sec_val have value below min_field_value we would wrongly report that address authentication is supported. It is not a big issue because we enable address authentication based on boot cpu (and check there is correct). Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> --- arch/arm64/kernel/cpufeature.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c index a46ab3b..b0ec125 100644 --- a/arch/arm64/kernel/cpufeature.c +++ b/arch/arm64/kernel/cpufeature.c @@ -1826,7 +1826,7 @@ static bool has_address_auth_cpucap(const struct arm64_cpu_capabilities *entry, /* Now check for the secondary CPUs with SCOPE_LOCAL_CPU scope */ sec_val = cpuid_feature_extract_field(__read_sysreg_by_encoding(entry->sys_reg), entry->field_pos, entry->sign); - return sec_val == boot_val; + return (sec_val >= entry->min_field_value) && (sec_val == boot_val); } static bool has_address_auth_metacap(const struct arm64_cpu_capabilities *entry, -- 2.7.4 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 16+ messages in thread
* Re: [PATCH v2 1/4] arm64: cpufeature: Account min_field_value when cheking secondaries for PAuth 2022-01-31 17:06 ` [PATCH v2 1/4] arm64: cpufeature: Account min_field_value when cheking secondaries for PAuth Vladimir Murzin @ 2022-02-04 18:13 ` Catalin Marinas 0 siblings, 0 replies; 16+ messages in thread From: Catalin Marinas @ 2022-02-04 18:13 UTC (permalink / raw) To: Vladimir Murzin; +Cc: linux-arm-kernel, maz, mark.rutland, will On Mon, Jan 31, 2022 at 05:06:51PM +0000, Vladimir Murzin wrote: > In case, both boot_val and sec_val have value below min_field_value we > would wrongly report that address authentication is supported. It is > not a big issue because we enable address authentication based on boot > cpu (and check there is correct). > > Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com> _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* [PATCH v2 2/4] arm64: cpufeature: Warn if mutually exclusive PAuth algorithms detected 2022-01-31 17:06 [PATCH v2 0/4] arm64: Support of PAuth QARMA3 architected algorithm Vladimir Murzin 2022-01-31 17:06 ` [PATCH v2 1/4] arm64: cpufeature: Account min_field_value when cheking secondaries for PAuth Vladimir Murzin @ 2022-01-31 17:06 ` Vladimir Murzin 2022-02-04 18:16 ` Catalin Marinas 2022-01-31 17:06 ` [PATCH v2 3/4] arm64: cpufeature: Mark existing PAuth architected algorithm as QARMA5 Vladimir Murzin ` (3 subsequent siblings) 5 siblings, 1 reply; 16+ messages in thread From: Vladimir Murzin @ 2022-01-31 17:06 UTC (permalink / raw) To: linux-arm-kernel; +Cc: maz, catalin.marinas, mark.rutland, will ARM ARM states for address authentication algorithms APA, bits [7:4] If the value of ID_AA64ISAR1_EL1.API is non-zero, this field must have the value 0b0000. API, bits [11:8] If the value of ID_AA64ISAR1_EL1.APA is non-zero, this field must have the value 0b0000. Similarly for generic code authentication algorithms GPA, bits [27:24] If the value of ID_AA64ISAR1_EL1.GPI is non-zero, this field must have the value 0b0000. GPI, bits [31:28] If the value of ID_AA64ISAR1_EL1.GPA is non-zero, this field must have the value 0b0000. Let's add a warning if that not true. Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> --- arch/arm64/kernel/cpufeature.c | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c index b0ec125..9dad0a3 100644 --- a/arch/arm64/kernel/cpufeature.c +++ b/arch/arm64/kernel/cpufeature.c @@ -1832,15 +1832,23 @@ static bool has_address_auth_cpucap(const struct arm64_cpu_capabilities *entry, static bool has_address_auth_metacap(const struct arm64_cpu_capabilities *entry, int scope) { - return has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH], scope) || - has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_IMP_DEF], scope); + bool api = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_IMP_DEF], scope); + bool apa = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH], scope); + + WARN_ON(apa && api); + + return apa || api; } static bool has_generic_auth(const struct arm64_cpu_capabilities *entry, int __unused) { - return __system_matches_cap(ARM64_HAS_GENERIC_AUTH_ARCH) || - __system_matches_cap(ARM64_HAS_GENERIC_AUTH_IMP_DEF); + bool gpi = __system_matches_cap(ARM64_HAS_GENERIC_AUTH_IMP_DEF); + bool gpa = __system_matches_cap(ARM64_HAS_GENERIC_AUTH_ARCH); + + WARN_ON(gpa && gpi); + + return gpa || gpi; } #endif /* CONFIG_ARM64_PTR_AUTH */ -- 2.7.4 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 16+ messages in thread
* Re: [PATCH v2 2/4] arm64: cpufeature: Warn if mutually exclusive PAuth algorithms detected 2022-01-31 17:06 ` [PATCH v2 2/4] arm64: cpufeature: Warn if mutually exclusive PAuth algorithms detected Vladimir Murzin @ 2022-02-04 18:16 ` Catalin Marinas 0 siblings, 0 replies; 16+ messages in thread From: Catalin Marinas @ 2022-02-04 18:16 UTC (permalink / raw) To: Vladimir Murzin; +Cc: linux-arm-kernel, maz, mark.rutland, will On Mon, Jan 31, 2022 at 05:06:52PM +0000, Vladimir Murzin wrote: > ARM ARM states for address authentication algorithms > > APA, bits [7:4] If the value of ID_AA64ISAR1_EL1.API is non-zero, this > field must have the value 0b0000. > > API, bits [11:8] If the value of ID_AA64ISAR1_EL1.APA is non-zero, > this field must have the value 0b0000. > > Similarly for generic code authentication algorithms > > GPA, bits [27:24] If the value of ID_AA64ISAR1_EL1.GPI is non-zero, > this field must have the value 0b0000. > > GPI, bits [31:28] If the value of ID_AA64ISAR1_EL1.GPA is non-zero, > this field must have the value 0b0000. > > Let's add a warning if that not true. > > Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> Acked-by: Catalin Marinas <catalin.marinas@arm.com> _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* [PATCH v2 3/4] arm64: cpufeature: Mark existing PAuth architected algorithm as QARMA5 2022-01-31 17:06 [PATCH v2 0/4] arm64: Support of PAuth QARMA3 architected algorithm Vladimir Murzin 2022-01-31 17:06 ` [PATCH v2 1/4] arm64: cpufeature: Account min_field_value when cheking secondaries for PAuth Vladimir Murzin 2022-01-31 17:06 ` [PATCH v2 2/4] arm64: cpufeature: Warn if mutually exclusive PAuth algorithms detected Vladimir Murzin @ 2022-01-31 17:06 ` Vladimir Murzin 2022-02-04 18:18 ` Catalin Marinas 2022-01-31 17:06 ` [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm Vladimir Murzin ` (2 subsequent siblings) 5 siblings, 1 reply; 16+ messages in thread From: Vladimir Murzin @ 2022-01-31 17:06 UTC (permalink / raw) To: linux-arm-kernel; +Cc: maz, catalin.marinas, mark.rutland, will In preparation of supporting PAuth QARMA3 architected algorithm mark existing one as QARMA5, so we can distingwish between two. Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> --- arch/arm64/kernel/cpufeature.c | 12 ++++++------ arch/arm64/tools/cpucaps | 4 ++-- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c index 9dad0a3..69fbc53 100644 --- a/arch/arm64/kernel/cpufeature.c +++ b/arch/arm64/kernel/cpufeature.c @@ -1833,7 +1833,7 @@ static bool has_address_auth_metacap(const struct arm64_cpu_capabilities *entry, int scope) { bool api = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_IMP_DEF], scope); - bool apa = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH], scope); + bool apa = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA5], scope); WARN_ON(apa && api); @@ -1844,7 +1844,7 @@ static bool has_generic_auth(const struct arm64_cpu_capabilities *entry, int __unused) { bool gpi = __system_matches_cap(ARM64_HAS_GENERIC_AUTH_IMP_DEF); - bool gpa = __system_matches_cap(ARM64_HAS_GENERIC_AUTH_ARCH); + bool gpa = __system_matches_cap(ARM64_HAS_GENERIC_AUTH_ARCH_QARMA5); WARN_ON(gpa && gpi); @@ -2235,8 +2235,8 @@ static const struct arm64_cpu_capabilities arm64_features[] = { }, #ifdef CONFIG_ARM64_PTR_AUTH { - .desc = "Address authentication (architected algorithm)", - .capability = ARM64_HAS_ADDRESS_AUTH_ARCH, + .desc = "Address authentication (architected QARMA5 algorithm)", + .capability = ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA5, .type = ARM64_CPUCAP_BOOT_CPU_FEATURE, .sys_reg = SYS_ID_AA64ISAR1_EL1, .sign = FTR_UNSIGNED, @@ -2260,8 +2260,8 @@ static const struct arm64_cpu_capabilities arm64_features[] = { .matches = has_address_auth_metacap, }, { - .desc = "Generic authentication (architected algorithm)", - .capability = ARM64_HAS_GENERIC_AUTH_ARCH, + .desc = "Generic authentication (architected QARMA5 algorithm)", + .capability = ARM64_HAS_GENERIC_AUTH_ARCH_QARMA5, .type = ARM64_CPUCAP_SYSTEM_FEATURE, .sys_reg = SYS_ID_AA64ISAR1_EL1, .sign = FTR_UNSIGNED, diff --git a/arch/arm64/tools/cpucaps b/arch/arm64/tools/cpucaps index 870c395..b1b6c40 100644 --- a/arch/arm64/tools/cpucaps +++ b/arch/arm64/tools/cpucaps @@ -7,7 +7,7 @@ BTI HAS_32BIT_EL0_DO_NOT_USE HAS_32BIT_EL1 HAS_ADDRESS_AUTH -HAS_ADDRESS_AUTH_ARCH +HAS_ADDRESS_AUTH_ARCH_QARMA5 HAS_ADDRESS_AUTH_IMP_DEF HAS_AMU_EXTN HAS_ARMv8_4_TTL @@ -21,7 +21,7 @@ HAS_E0PD HAS_ECV HAS_EPAN HAS_GENERIC_AUTH -HAS_GENERIC_AUTH_ARCH +HAS_GENERIC_AUTH_ARCH_QARMA5 HAS_GENERIC_AUTH_IMP_DEF HAS_IRQ_PRIO_MASKING HAS_LDAPR -- 2.7.4 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 16+ messages in thread
* Re: [PATCH v2 3/4] arm64: cpufeature: Mark existing PAuth architected algorithm as QARMA5 2022-01-31 17:06 ` [PATCH v2 3/4] arm64: cpufeature: Mark existing PAuth architected algorithm as QARMA5 Vladimir Murzin @ 2022-02-04 18:18 ` Catalin Marinas 0 siblings, 0 replies; 16+ messages in thread From: Catalin Marinas @ 2022-02-04 18:18 UTC (permalink / raw) To: Vladimir Murzin; +Cc: linux-arm-kernel, maz, mark.rutland, will On Mon, Jan 31, 2022 at 05:06:53PM +0000, Vladimir Murzin wrote: > In preparation of supporting PAuth QARMA3 architected algorithm mark > existing one as QARMA5, so we can distingwish between two. > > Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> Acked-by: Catalin Marinas <catalin.marinas@arm.com> _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm 2022-01-31 17:06 [PATCH v2 0/4] arm64: Support of PAuth QARMA3 architected algorithm Vladimir Murzin ` (2 preceding siblings ...) 2022-01-31 17:06 ` [PATCH v2 3/4] arm64: cpufeature: Mark existing PAuth architected algorithm as QARMA5 Vladimir Murzin @ 2022-01-31 17:06 ` Vladimir Murzin 2022-02-04 18:42 ` Catalin Marinas 2022-02-15 18:21 ` Will Deacon 2022-01-31 17:38 ` [PATCH v2 0/4] arm64: Support " Vladimir Murzin 2022-02-05 10:27 ` Marc Zyngier 5 siblings, 2 replies; 16+ messages in thread From: Vladimir Murzin @ 2022-01-31 17:06 UTC (permalink / raw) To: linux-arm-kernel; +Cc: maz, catalin.marinas, mark.rutland, will QARMA3 is relaxed version of the QARMA5 algorithm which expected to reduce the latency of calculation while still delivering a suitable level of security. Support for QARMA3 can be discovered via ID_AA64ISAR2_EL1 APA3, bits [15:12] Indicates whether the QARMA3 algorithm is implemented in the PE for address authentication in AArch64 state. GPA3, bits [11:8] Indicates whether the QARMA3 algorithm is implemented in the PE for generic code authentication in AArch64 state. Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> --- arch/arm64/include/asm/asm_pointer_auth.h | 3 ++ arch/arm64/include/asm/cpufeature.h | 1 + arch/arm64/include/asm/kvm_hyp.h | 1 + arch/arm64/include/asm/sysreg.h | 12 +++++++ arch/arm64/kernel/cpufeature.c | 45 +++++++++++++++++++++++--- arch/arm64/kernel/idreg-override.c | 16 +++++++-- arch/arm64/kvm/arm.c | 1 + arch/arm64/kvm/hyp/include/nvhe/fixed_config.h | 5 +++ arch/arm64/kvm/hyp/nvhe/sys_regs.c | 14 ++++++++ arch/arm64/kvm/sys_regs.c | 5 +++ arch/arm64/tools/cpucaps | 2 ++ 11 files changed, 99 insertions(+), 6 deletions(-) diff --git a/arch/arm64/include/asm/asm_pointer_auth.h b/arch/arm64/include/asm/asm_pointer_auth.h index f1bba5f..ead62f7 100644 --- a/arch/arm64/include/asm/asm_pointer_auth.h +++ b/arch/arm64/include/asm/asm_pointer_auth.h @@ -60,6 +60,9 @@ alternative_else_nop_endif .macro __ptrauth_keys_init_cpu tsk, tmp1, tmp2, tmp3 mrs \tmp1, id_aa64isar1_el1 ubfx \tmp1, \tmp1, #ID_AA64ISAR1_APA_SHIFT, #8 + mrs_s \tmp2, SYS_ID_AA64ISAR2_EL1 + ubfx \tmp2, \tmp2, #ID_AA64ISAR2_APA3_SHIFT, #4 + orr \tmp1, \tmp1, \tmp2 cbz \tmp1, .Lno_addr_auth\@ mov_q \tmp1, (SCTLR_ELx_ENIA | SCTLR_ELx_ENIB | \ SCTLR_ELx_ENDA | SCTLR_ELx_ENDB) diff --git a/arch/arm64/include/asm/cpufeature.h b/arch/arm64/include/asm/cpufeature.h index ef6be92..fe7137f 100644 --- a/arch/arm64/include/asm/cpufeature.h +++ b/arch/arm64/include/asm/cpufeature.h @@ -854,6 +854,7 @@ static inline unsigned int get_vmid_bits(u64 mmfr1) extern struct arm64_ftr_override id_aa64mmfr1_override; extern struct arm64_ftr_override id_aa64pfr1_override; extern struct arm64_ftr_override id_aa64isar1_override; +extern struct arm64_ftr_override id_aa64isar2_override; u32 get_kvm_ipa_limit(void); void dump_cpu_features(void); diff --git a/arch/arm64/include/asm/kvm_hyp.h b/arch/arm64/include/asm/kvm_hyp.h index 462882f..aa7fa2a 100644 --- a/arch/arm64/include/asm/kvm_hyp.h +++ b/arch/arm64/include/asm/kvm_hyp.h @@ -118,6 +118,7 @@ extern u64 kvm_nvhe_sym(id_aa64pfr0_el1_sys_val); extern u64 kvm_nvhe_sym(id_aa64pfr1_el1_sys_val); extern u64 kvm_nvhe_sym(id_aa64isar0_el1_sys_val); extern u64 kvm_nvhe_sym(id_aa64isar1_el1_sys_val); +extern u64 kvm_nvhe_sym(id_aa64isar2_el1_sys_val); extern u64 kvm_nvhe_sym(id_aa64mmfr0_el1_sys_val); extern u64 kvm_nvhe_sym(id_aa64mmfr1_el1_sys_val); extern u64 kvm_nvhe_sym(id_aa64mmfr2_el1_sys_val); diff --git a/arch/arm64/include/asm/sysreg.h b/arch/arm64/include/asm/sysreg.h index 898bee0..cbe4164 100644 --- a/arch/arm64/include/asm/sysreg.h +++ b/arch/arm64/include/asm/sysreg.h @@ -773,6 +773,8 @@ #define ID_AA64ISAR1_GPI_IMP_DEF 0x1 /* id_aa64isar2 */ +#define ID_AA64ISAR2_APA3_SHIFT 12 +#define ID_AA64ISAR2_GPA3_SHIFT 8 #define ID_AA64ISAR2_RPRES_SHIFT 4 #define ID_AA64ISAR2_WFXT_SHIFT 0 @@ -786,6 +788,16 @@ #define ID_AA64ISAR2_WFXT_NI 0x0 #define ID_AA64ISAR2_WFXT_SUPPORTED 0x2 +#define ID_AA64ISAR2_APA3_NI 0x0 +#define ID_AA64ISAR2_APA3_ARCHITECTED 0x1 +#define ID_AA64ISAR2_APA3_ARCH_EPAC 0x2 +#define ID_AA64ISAR2_APA3_ARCH_EPAC2 0x3 +#define ID_AA64ISAR2_APA3_ARCH_EPAC2_FPAC 0x4 +#define ID_AA64ISAR2_APA3_ARCH_EPAC2_FPAC_CMB 0x5 + +#define ID_AA64ISAR2_GPA3_NI 0x0 +#define ID_AA64ISAR2_GPA3_ARCHITECTED 0x1 + /* id_aa64pfr0 */ #define ID_AA64PFR0_CSV3_SHIFT 60 #define ID_AA64PFR0_CSV2_SHIFT 56 diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c index 69fbc53..aab6766 100644 --- a/arch/arm64/kernel/cpufeature.c +++ b/arch/arm64/kernel/cpufeature.c @@ -226,6 +226,10 @@ static const struct arm64_ftr_bits ftr_id_aa64isar1[] = { }; static const struct arm64_ftr_bits ftr_id_aa64isar2[] = { + ARM64_FTR_BITS(FTR_VISIBLE_IF_IS_ENABLED(CONFIG_ARM64_PTR_AUTH), + FTR_STRICT, FTR_EXACT, ID_AA64ISAR2_APA3_SHIFT, 4, 0), + ARM64_FTR_BITS(FTR_VISIBLE_IF_IS_ENABLED(CONFIG_ARM64_PTR_AUTH), + FTR_STRICT, FTR_LOWER_SAFE, ID_AA64ISAR2_GPA3_SHIFT, 4, 0), ARM64_FTR_BITS(FTR_VISIBLE, FTR_NONSTRICT, FTR_LOWER_SAFE, ID_AA64ISAR2_RPRES_SHIFT, 4, 0), ARM64_FTR_END, }; @@ -596,6 +600,7 @@ static const struct arm64_ftr_bits ftr_raz[] = { struct arm64_ftr_override __ro_after_init id_aa64mmfr1_override; struct arm64_ftr_override __ro_after_init id_aa64pfr1_override; struct arm64_ftr_override __ro_after_init id_aa64isar1_override; +struct arm64_ftr_override __ro_after_init id_aa64isar2_override; static const struct __ftr_reg_entry { u32 sys_id; @@ -644,6 +649,8 @@ static const struct __ftr_reg_entry { ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR1_EL1, ftr_id_aa64isar1, &id_aa64isar1_override), ARM64_FTR_REG(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2), + ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2, + &id_aa64isar2_override), /* Op1 = 0, CRn = 0, CRm = 7 */ ARM64_FTR_REG(SYS_ID_AA64MMFR0_EL1, ftr_id_aa64mmfr0), @@ -1834,10 +1841,11 @@ static bool has_address_auth_metacap(const struct arm64_cpu_capabilities *entry, { bool api = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_IMP_DEF], scope); bool apa = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA5], scope); + bool apa3 = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA3], scope); - WARN_ON(apa && api); + WARN_ON((apa && api) || (apa && apa3) || (api && apa3)); - return apa || api; + return apa || apa3 || api; } static bool has_generic_auth(const struct arm64_cpu_capabilities *entry, @@ -1845,10 +1853,11 @@ static bool has_generic_auth(const struct arm64_cpu_capabilities *entry, { bool gpi = __system_matches_cap(ARM64_HAS_GENERIC_AUTH_IMP_DEF); bool gpa = __system_matches_cap(ARM64_HAS_GENERIC_AUTH_ARCH_QARMA5); + bool gpa3 = __system_matches_cap(ARM64_HAS_GENERIC_AUTH_ARCH_QARMA3); - WARN_ON(gpa && gpi); + WARN_ON((gpa && gpi) || (gpa && gpa3) || (gpi && gpa3)); - return gpa || gpi; + return gpa || gpa3 || gpi; } #endif /* CONFIG_ARM64_PTR_AUTH */ @@ -2245,6 +2254,16 @@ static const struct arm64_cpu_capabilities arm64_features[] = { .matches = has_address_auth_cpucap, }, { + .desc = "Address authentication (architected QARMA3 algorithm)", + .capability = ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA3, + .type = ARM64_CPUCAP_BOOT_CPU_FEATURE, + .sys_reg = SYS_ID_AA64ISAR2_EL1, + .sign = FTR_UNSIGNED, + .field_pos = ID_AA64ISAR2_APA3_SHIFT, + .min_field_value = ID_AA64ISAR2_APA3_ARCHITECTED, + .matches = has_address_auth_cpucap, + }, + { .desc = "Address authentication (IMP DEF algorithm)", .capability = ARM64_HAS_ADDRESS_AUTH_IMP_DEF, .type = ARM64_CPUCAP_BOOT_CPU_FEATURE, @@ -2270,6 +2289,16 @@ static const struct arm64_cpu_capabilities arm64_features[] = { .matches = has_cpuid_feature, }, { + .desc = "Generic authentication (architected QARMA3 algorithm)", + .capability = ARM64_HAS_GENERIC_AUTH_ARCH_QARMA3, + .type = ARM64_CPUCAP_SYSTEM_FEATURE, + .sys_reg = SYS_ID_AA64ISAR2_EL1, + .sign = FTR_UNSIGNED, + .field_pos = ID_AA64ISAR2_GPA3_SHIFT, + .min_field_value = ID_AA64ISAR2_GPA3_ARCHITECTED, + .matches = has_cpuid_feature, + }, + { .desc = "Generic authentication (IMP DEF algorithm)", .capability = ARM64_HAS_GENERIC_AUTH_IMP_DEF, .type = ARM64_CPUCAP_SYSTEM_FEATURE, @@ -2417,6 +2446,10 @@ static const struct arm64_cpu_capabilities ptr_auth_hwcap_addr_matches[] = { FTR_UNSIGNED, ID_AA64ISAR1_APA_ARCHITECTED) }, { + HWCAP_CPUID_MATCH(SYS_ID_AA64ISAR2_EL1, ID_AA64ISAR2_APA3_SHIFT, + FTR_UNSIGNED, ID_AA64ISAR2_APA3_ARCHITECTED) + }, + { HWCAP_CPUID_MATCH(SYS_ID_AA64ISAR1_EL1, ID_AA64ISAR1_API_SHIFT, FTR_UNSIGNED, ID_AA64ISAR1_API_IMP_DEF) }, @@ -2429,6 +2462,10 @@ static const struct arm64_cpu_capabilities ptr_auth_hwcap_gen_matches[] = { FTR_UNSIGNED, ID_AA64ISAR1_GPA_ARCHITECTED) }, { + HWCAP_CPUID_MATCH(SYS_ID_AA64ISAR2_EL1, ID_AA64ISAR2_GPA3_SHIFT, + FTR_UNSIGNED, ID_AA64ISAR2_GPA3_ARCHITECTED) + }, + { HWCAP_CPUID_MATCH(SYS_ID_AA64ISAR1_EL1, ID_AA64ISAR1_GPI_SHIFT, FTR_UNSIGNED, ID_AA64ISAR1_GPI_IMP_DEF) }, diff --git a/arch/arm64/kernel/idreg-override.c b/arch/arm64/kernel/idreg-override.c index d8e606f..8a2ceb5 100644 --- a/arch/arm64/kernel/idreg-override.c +++ b/arch/arm64/kernel/idreg-override.c @@ -17,7 +17,7 @@ #define FTR_DESC_NAME_LEN 20 #define FTR_DESC_FIELD_LEN 10 #define FTR_ALIAS_NAME_LEN 30 -#define FTR_ALIAS_OPTION_LEN 80 +#define FTR_ALIAS_OPTION_LEN 116 struct ftr_set_desc { char name[FTR_DESC_NAME_LEN]; @@ -71,6 +71,16 @@ static const struct ftr_set_desc isar1 __initconst = { }, }; +static const struct ftr_set_desc isar2 __initconst = { + .name = "id_aa64isar2", + .override = &id_aa64isar2_override, + .fields = { + { "gpa3", ID_AA64ISAR2_GPA3_SHIFT }, + { "apa3", ID_AA64ISAR2_APA3_SHIFT }, + {} + }, +}; + extern struct arm64_ftr_override kaslr_feature_override; static const struct ftr_set_desc kaslr __initconst = { @@ -88,6 +98,7 @@ static const struct ftr_set_desc * const regs[] __initconst = { &mmfr1, &pfr1, &isar1, + &isar2, &kaslr, }; @@ -100,7 +111,8 @@ static const struct { { "arm64.nobti", "id_aa64pfr1.bt=0" }, { "arm64.nopauth", "id_aa64isar1.gpi=0 id_aa64isar1.gpa=0 " - "id_aa64isar1.api=0 id_aa64isar1.apa=0" }, + "id_aa64isar1.api=0 id_aa64isar1.apa=0 " + "id_aa64isar2.gpa3=0 id_aa64isar2.apa3=0" }, { "arm64.nomte", "id_aa64pfr1.mte=0" }, { "nokaslr", "kaslr.disabled=1" }, }; diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c index a4a0063..a08bc68 100644 --- a/arch/arm64/kvm/arm.c +++ b/arch/arm64/kvm/arm.c @@ -1855,6 +1855,7 @@ static int kvm_hyp_init_protection(u32 hyp_va_bits) kvm_nvhe_sym(id_aa64pfr1_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64PFR1_EL1); kvm_nvhe_sym(id_aa64isar0_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64ISAR0_EL1); kvm_nvhe_sym(id_aa64isar1_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64ISAR1_EL1); + kvm_nvhe_sym(id_aa64isar2_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64ISAR2_EL1); kvm_nvhe_sym(id_aa64mmfr0_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64MMFR0_EL1); kvm_nvhe_sym(id_aa64mmfr1_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64MMFR1_EL1); kvm_nvhe_sym(id_aa64mmfr2_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64MMFR2_EL1); diff --git a/arch/arm64/kvm/hyp/include/nvhe/fixed_config.h b/arch/arm64/kvm/hyp/include/nvhe/fixed_config.h index eea1f6a..5ad6265 100644 --- a/arch/arm64/kvm/hyp/include/nvhe/fixed_config.h +++ b/arch/arm64/kvm/hyp/include/nvhe/fixed_config.h @@ -192,6 +192,11 @@ ARM64_FEATURE_MASK(ID_AA64ISAR1_I8MM) \ ) +#define PVM_ID_AA64ISAR2_ALLOW (\ + ARM64_FEATURE_MASK(ID_AA64ISAR2_GPA3) | \ + ARM64_FEATURE_MASK(ID_AA64ISAR2_APA3) \ + ) + u64 pvm_read_id_reg(const struct kvm_vcpu *vcpu, u32 id); bool kvm_handle_pvm_sysreg(struct kvm_vcpu *vcpu, u64 *exit_code); bool kvm_handle_pvm_restricted(struct kvm_vcpu *vcpu, u64 *exit_code); diff --git a/arch/arm64/kvm/hyp/nvhe/sys_regs.c b/arch/arm64/kvm/hyp/nvhe/sys_regs.c index 792cf6e..33f5181 100644 --- a/arch/arm64/kvm/hyp/nvhe/sys_regs.c +++ b/arch/arm64/kvm/hyp/nvhe/sys_regs.c @@ -22,6 +22,7 @@ u64 id_aa64pfr0_el1_sys_val; u64 id_aa64pfr1_el1_sys_val; u64 id_aa64isar0_el1_sys_val; u64 id_aa64isar1_el1_sys_val; +u64 id_aa64isar2_el1_sys_val; u64 id_aa64mmfr0_el1_sys_val; u64 id_aa64mmfr1_el1_sys_val; u64 id_aa64mmfr2_el1_sys_val; @@ -183,6 +184,17 @@ static u64 get_pvm_id_aa64isar1(const struct kvm_vcpu *vcpu) return id_aa64isar1_el1_sys_val & allow_mask; } +static u64 get_pvm_id_aa64isar2(const struct kvm_vcpu *vcpu) +{ + u64 allow_mask = PVM_ID_AA64ISAR2_ALLOW; + + if (!vcpu_has_ptrauth(vcpu)) + allow_mask &= ~(ARM64_FEATURE_MASK(ID_AA64ISAR2_APA3) | + ARM64_FEATURE_MASK(ID_AA64ISAR2_GPA3)); + + return id_aa64isar2_el1_sys_val & allow_mask; +} + static u64 get_pvm_id_aa64mmfr0(const struct kvm_vcpu *vcpu) { u64 set_mask; @@ -225,6 +237,8 @@ u64 pvm_read_id_reg(const struct kvm_vcpu *vcpu, u32 id) return get_pvm_id_aa64isar0(vcpu); case SYS_ID_AA64ISAR1_EL1: return get_pvm_id_aa64isar1(vcpu); + case SYS_ID_AA64ISAR2_EL1: + return get_pvm_id_aa64isar2(vcpu); case SYS_ID_AA64MMFR0_EL1: return get_pvm_id_aa64mmfr0(vcpu); case SYS_ID_AA64MMFR1_EL1: diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c index 4dc2fba..baa6529 100644 --- a/arch/arm64/kvm/sys_regs.c +++ b/arch/arm64/kvm/sys_regs.c @@ -1097,6 +1097,11 @@ static u64 read_id_reg(const struct kvm_vcpu *vcpu, ARM64_FEATURE_MASK(ID_AA64ISAR1_GPA) | ARM64_FEATURE_MASK(ID_AA64ISAR1_GPI)); break; + case SYS_ID_AA64ISAR2_EL1: + if (!vcpu_has_ptrauth(vcpu)) + val &= ~(ARM64_FEATURE_MASK(ID_AA64ISAR2_APA3) | + ARM64_FEATURE_MASK(ID_AA64ISAR2_GPA3)); + break; case SYS_ID_AA64DFR0_EL1: /* Limit debug to ARMv8.0 */ val &= ~ARM64_FEATURE_MASK(ID_AA64DFR0_DEBUGVER); diff --git a/arch/arm64/tools/cpucaps b/arch/arm64/tools/cpucaps index b1b6c40..f2afe9a 100644 --- a/arch/arm64/tools/cpucaps +++ b/arch/arm64/tools/cpucaps @@ -7,6 +7,7 @@ BTI HAS_32BIT_EL0_DO_NOT_USE HAS_32BIT_EL1 HAS_ADDRESS_AUTH +HAS_ADDRESS_AUTH_ARCH_QARMA3 HAS_ADDRESS_AUTH_ARCH_QARMA5 HAS_ADDRESS_AUTH_IMP_DEF HAS_AMU_EXTN @@ -21,6 +22,7 @@ HAS_E0PD HAS_ECV HAS_EPAN HAS_GENERIC_AUTH +HAS_GENERIC_AUTH_ARCH_QARMA3 HAS_GENERIC_AUTH_ARCH_QARMA5 HAS_GENERIC_AUTH_IMP_DEF HAS_IRQ_PRIO_MASKING -- 2.7.4 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 16+ messages in thread
* Re: [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm 2022-01-31 17:06 ` [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm Vladimir Murzin @ 2022-02-04 18:42 ` Catalin Marinas 2022-02-15 18:21 ` Will Deacon 1 sibling, 0 replies; 16+ messages in thread From: Catalin Marinas @ 2022-02-04 18:42 UTC (permalink / raw) To: Vladimir Murzin; +Cc: linux-arm-kernel, maz, mark.rutland, will On Mon, Jan 31, 2022 at 05:06:54PM +0000, Vladimir Murzin wrote: > QARMA3 is relaxed version of the QARMA5 algorithm which expected to > reduce the latency of calculation while still delivering a suitable > level of security. > > Support for QARMA3 can be discovered via ID_AA64ISAR2_EL1 > > APA3, bits [15:12] Indicates whether the QARMA3 algorithm is > implemented in the PE for address > authentication in AArch64 state. > > GPA3, bits [11:8] Indicates whether the QARMA3 algorithm is > implemented in the PE for generic code > authentication in AArch64 state. > > Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> > --- > arch/arm64/include/asm/asm_pointer_auth.h | 3 ++ > arch/arm64/include/asm/cpufeature.h | 1 + > arch/arm64/include/asm/kvm_hyp.h | 1 + > arch/arm64/include/asm/sysreg.h | 12 +++++++ > arch/arm64/kernel/cpufeature.c | 45 +++++++++++++++++++++++--- > arch/arm64/kernel/idreg-override.c | 16 +++++++-- > arch/arm64/kvm/arm.c | 1 + > arch/arm64/kvm/hyp/include/nvhe/fixed_config.h | 5 +++ > arch/arm64/kvm/hyp/nvhe/sys_regs.c | 14 ++++++++ > arch/arm64/kvm/sys_regs.c | 5 +++ > arch/arm64/tools/cpucaps | 2 ++ > 11 files changed, 99 insertions(+), 6 deletions(-) For the non-KVM bits: Reviewed-by: Catalin Marinas <catalin.marinas@arm.com> _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm 2022-01-31 17:06 ` [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm Vladimir Murzin 2022-02-04 18:42 ` Catalin Marinas @ 2022-02-15 18:21 ` Will Deacon 2022-02-21 14:47 ` Vladimir Murzin 1 sibling, 1 reply; 16+ messages in thread From: Will Deacon @ 2022-02-15 18:21 UTC (permalink / raw) To: Vladimir Murzin; +Cc: linux-arm-kernel, maz, catalin.marinas, mark.rutland On Mon, Jan 31, 2022 at 05:06:54PM +0000, Vladimir Murzin wrote: > QARMA3 is relaxed version of the QARMA5 algorithm which expected to > reduce the latency of calculation while still delivering a suitable > level of security. > > Support for QARMA3 can be discovered via ID_AA64ISAR2_EL1 > > APA3, bits [15:12] Indicates whether the QARMA3 algorithm is > implemented in the PE for address > authentication in AArch64 state. > > GPA3, bits [11:8] Indicates whether the QARMA3 algorithm is > implemented in the PE for generic code > authentication in AArch64 state. > > Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> > --- > arch/arm64/include/asm/asm_pointer_auth.h | 3 ++ > arch/arm64/include/asm/cpufeature.h | 1 + > arch/arm64/include/asm/kvm_hyp.h | 1 + > arch/arm64/include/asm/sysreg.h | 12 +++++++ > arch/arm64/kernel/cpufeature.c | 45 +++++++++++++++++++++++--- > arch/arm64/kernel/idreg-override.c | 16 +++++++-- > arch/arm64/kvm/arm.c | 1 + > arch/arm64/kvm/hyp/include/nvhe/fixed_config.h | 5 +++ > arch/arm64/kvm/hyp/nvhe/sys_regs.c | 14 ++++++++ > arch/arm64/kvm/sys_regs.c | 5 +++ > arch/arm64/tools/cpucaps | 2 ++ > 11 files changed, 99 insertions(+), 6 deletions(-) > > diff --git a/arch/arm64/include/asm/asm_pointer_auth.h b/arch/arm64/include/asm/asm_pointer_auth.h > index f1bba5f..ead62f7 100644 > --- a/arch/arm64/include/asm/asm_pointer_auth.h > +++ b/arch/arm64/include/asm/asm_pointer_auth.h > @@ -60,6 +60,9 @@ alternative_else_nop_endif > .macro __ptrauth_keys_init_cpu tsk, tmp1, tmp2, tmp3 > mrs \tmp1, id_aa64isar1_el1 > ubfx \tmp1, \tmp1, #ID_AA64ISAR1_APA_SHIFT, #8 > + mrs_s \tmp2, SYS_ID_AA64ISAR2_EL1 > + ubfx \tmp2, \tmp2, #ID_AA64ISAR2_APA3_SHIFT, #4 > + orr \tmp1, \tmp1, \tmp2 > cbz \tmp1, .Lno_addr_auth\@ > mov_q \tmp1, (SCTLR_ELx_ENIA | SCTLR_ELx_ENIB | \ > SCTLR_ELx_ENDA | SCTLR_ELx_ENDB) > diff --git a/arch/arm64/include/asm/cpufeature.h b/arch/arm64/include/asm/cpufeature.h > index ef6be92..fe7137f 100644 > --- a/arch/arm64/include/asm/cpufeature.h > +++ b/arch/arm64/include/asm/cpufeature.h > @@ -854,6 +854,7 @@ static inline unsigned int get_vmid_bits(u64 mmfr1) > extern struct arm64_ftr_override id_aa64mmfr1_override; > extern struct arm64_ftr_override id_aa64pfr1_override; > extern struct arm64_ftr_override id_aa64isar1_override; > +extern struct arm64_ftr_override id_aa64isar2_override; > > u32 get_kvm_ipa_limit(void); > void dump_cpu_features(void); > diff --git a/arch/arm64/include/asm/kvm_hyp.h b/arch/arm64/include/asm/kvm_hyp.h > index 462882f..aa7fa2a 100644 > --- a/arch/arm64/include/asm/kvm_hyp.h > +++ b/arch/arm64/include/asm/kvm_hyp.h > @@ -118,6 +118,7 @@ extern u64 kvm_nvhe_sym(id_aa64pfr0_el1_sys_val); > extern u64 kvm_nvhe_sym(id_aa64pfr1_el1_sys_val); > extern u64 kvm_nvhe_sym(id_aa64isar0_el1_sys_val); > extern u64 kvm_nvhe_sym(id_aa64isar1_el1_sys_val); > +extern u64 kvm_nvhe_sym(id_aa64isar2_el1_sys_val); > extern u64 kvm_nvhe_sym(id_aa64mmfr0_el1_sys_val); > extern u64 kvm_nvhe_sym(id_aa64mmfr1_el1_sys_val); > extern u64 kvm_nvhe_sym(id_aa64mmfr2_el1_sys_val); > diff --git a/arch/arm64/include/asm/sysreg.h b/arch/arm64/include/asm/sysreg.h > index 898bee0..cbe4164 100644 > --- a/arch/arm64/include/asm/sysreg.h > +++ b/arch/arm64/include/asm/sysreg.h > @@ -773,6 +773,8 @@ > #define ID_AA64ISAR1_GPI_IMP_DEF 0x1 > > /* id_aa64isar2 */ > +#define ID_AA64ISAR2_APA3_SHIFT 12 > +#define ID_AA64ISAR2_GPA3_SHIFT 8 > #define ID_AA64ISAR2_RPRES_SHIFT 4 > #define ID_AA64ISAR2_WFXT_SHIFT 0 > > @@ -786,6 +788,16 @@ > #define ID_AA64ISAR2_WFXT_NI 0x0 > #define ID_AA64ISAR2_WFXT_SUPPORTED 0x2 > > +#define ID_AA64ISAR2_APA3_NI 0x0 > +#define ID_AA64ISAR2_APA3_ARCHITECTED 0x1 > +#define ID_AA64ISAR2_APA3_ARCH_EPAC 0x2 > +#define ID_AA64ISAR2_APA3_ARCH_EPAC2 0x3 > +#define ID_AA64ISAR2_APA3_ARCH_EPAC2_FPAC 0x4 > +#define ID_AA64ISAR2_APA3_ARCH_EPAC2_FPAC_CMB 0x5 > + > +#define ID_AA64ISAR2_GPA3_NI 0x0 > +#define ID_AA64ISAR2_GPA3_ARCHITECTED 0x1 > + > /* id_aa64pfr0 */ > #define ID_AA64PFR0_CSV3_SHIFT 60 > #define ID_AA64PFR0_CSV2_SHIFT 56 > diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c > index 69fbc53..aab6766 100644 > --- a/arch/arm64/kernel/cpufeature.c > +++ b/arch/arm64/kernel/cpufeature.c > @@ -226,6 +226,10 @@ static const struct arm64_ftr_bits ftr_id_aa64isar1[] = { > }; > > static const struct arm64_ftr_bits ftr_id_aa64isar2[] = { > + ARM64_FTR_BITS(FTR_VISIBLE_IF_IS_ENABLED(CONFIG_ARM64_PTR_AUTH), > + FTR_STRICT, FTR_EXACT, ID_AA64ISAR2_APA3_SHIFT, 4, 0), > + ARM64_FTR_BITS(FTR_VISIBLE_IF_IS_ENABLED(CONFIG_ARM64_PTR_AUTH), > + FTR_STRICT, FTR_LOWER_SAFE, ID_AA64ISAR2_GPA3_SHIFT, 4, 0), > ARM64_FTR_BITS(FTR_VISIBLE, FTR_NONSTRICT, FTR_LOWER_SAFE, ID_AA64ISAR2_RPRES_SHIFT, 4, 0), > ARM64_FTR_END, > }; > @@ -596,6 +600,7 @@ static const struct arm64_ftr_bits ftr_raz[] = { > struct arm64_ftr_override __ro_after_init id_aa64mmfr1_override; > struct arm64_ftr_override __ro_after_init id_aa64pfr1_override; > struct arm64_ftr_override __ro_after_init id_aa64isar1_override; > +struct arm64_ftr_override __ro_after_init id_aa64isar2_override; > > static const struct __ftr_reg_entry { > u32 sys_id; > @@ -644,6 +649,8 @@ static const struct __ftr_reg_entry { > ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR1_EL1, ftr_id_aa64isar1, > &id_aa64isar1_override), > ARM64_FTR_REG(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2), > + ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2, > + &id_aa64isar2_override), > > /* Op1 = 0, CRn = 0, CRm = 7 */ > ARM64_FTR_REG(SYS_ID_AA64MMFR0_EL1, ftr_id_aa64mmfr0), > @@ -1834,10 +1841,11 @@ static bool has_address_auth_metacap(const struct arm64_cpu_capabilities *entry, > { > bool api = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_IMP_DEF], scope); > bool apa = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA5], scope); > + bool apa3 = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA3], scope); > > - WARN_ON(apa && api); > + WARN_ON((apa && api) || (apa && apa3) || (api && apa3)); I don't really get the point in this warning, what is somebody supposed to do if they hit it? The kernel isn't the right place to make assertions about the CPU design. Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm 2022-02-15 18:21 ` Will Deacon @ 2022-02-21 14:47 ` Vladimir Murzin 2022-02-22 21:50 ` Will Deacon 0 siblings, 1 reply; 16+ messages in thread From: Vladimir Murzin @ 2022-02-21 14:47 UTC (permalink / raw) To: Will Deacon; +Cc: linux-arm-kernel, maz, catalin.marinas, mark.rutland On 2/15/22 6:21 PM, Will Deacon wrote: > On Mon, Jan 31, 2022 at 05:06:54PM +0000, Vladimir Murzin wrote: >> QARMA3 is relaxed version of the QARMA5 algorithm which expected to >> reduce the latency of calculation while still delivering a suitable >> level of security. >> >> Support for QARMA3 can be discovered via ID_AA64ISAR2_EL1 >> >> APA3, bits [15:12] Indicates whether the QARMA3 algorithm is >> implemented in the PE for address >> authentication in AArch64 state. >> >> GPA3, bits [11:8] Indicates whether the QARMA3 algorithm is >> implemented in the PE for generic code >> authentication in AArch64 state. >> >> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> >> --- >> arch/arm64/include/asm/asm_pointer_auth.h | 3 ++ >> arch/arm64/include/asm/cpufeature.h | 1 + >> arch/arm64/include/asm/kvm_hyp.h | 1 + >> arch/arm64/include/asm/sysreg.h | 12 +++++++ >> arch/arm64/kernel/cpufeature.c | 45 +++++++++++++++++++++++--- >> arch/arm64/kernel/idreg-override.c | 16 +++++++-- >> arch/arm64/kvm/arm.c | 1 + >> arch/arm64/kvm/hyp/include/nvhe/fixed_config.h | 5 +++ >> arch/arm64/kvm/hyp/nvhe/sys_regs.c | 14 ++++++++ >> arch/arm64/kvm/sys_regs.c | 5 +++ >> arch/arm64/tools/cpucaps | 2 ++ >> 11 files changed, 99 insertions(+), 6 deletions(-) >> >> diff --git a/arch/arm64/include/asm/asm_pointer_auth.h b/arch/arm64/include/asm/asm_pointer_auth.h >> index f1bba5f..ead62f7 100644 >> --- a/arch/arm64/include/asm/asm_pointer_auth.h >> +++ b/arch/arm64/include/asm/asm_pointer_auth.h >> @@ -60,6 +60,9 @@ alternative_else_nop_endif >> .macro __ptrauth_keys_init_cpu tsk, tmp1, tmp2, tmp3 >> mrs \tmp1, id_aa64isar1_el1 >> ubfx \tmp1, \tmp1, #ID_AA64ISAR1_APA_SHIFT, #8 >> + mrs_s \tmp2, SYS_ID_AA64ISAR2_EL1 >> + ubfx \tmp2, \tmp2, #ID_AA64ISAR2_APA3_SHIFT, #4 >> + orr \tmp1, \tmp1, \tmp2 >> cbz \tmp1, .Lno_addr_auth\@ >> mov_q \tmp1, (SCTLR_ELx_ENIA | SCTLR_ELx_ENIB | \ >> SCTLR_ELx_ENDA | SCTLR_ELx_ENDB) >> diff --git a/arch/arm64/include/asm/cpufeature.h b/arch/arm64/include/asm/cpufeature.h >> index ef6be92..fe7137f 100644 >> --- a/arch/arm64/include/asm/cpufeature.h >> +++ b/arch/arm64/include/asm/cpufeature.h >> @@ -854,6 +854,7 @@ static inline unsigned int get_vmid_bits(u64 mmfr1) >> extern struct arm64_ftr_override id_aa64mmfr1_override; >> extern struct arm64_ftr_override id_aa64pfr1_override; >> extern struct arm64_ftr_override id_aa64isar1_override; >> +extern struct arm64_ftr_override id_aa64isar2_override; >> >> u32 get_kvm_ipa_limit(void); >> void dump_cpu_features(void); >> diff --git a/arch/arm64/include/asm/kvm_hyp.h b/arch/arm64/include/asm/kvm_hyp.h >> index 462882f..aa7fa2a 100644 >> --- a/arch/arm64/include/asm/kvm_hyp.h >> +++ b/arch/arm64/include/asm/kvm_hyp.h >> @@ -118,6 +118,7 @@ extern u64 kvm_nvhe_sym(id_aa64pfr0_el1_sys_val); >> extern u64 kvm_nvhe_sym(id_aa64pfr1_el1_sys_val); >> extern u64 kvm_nvhe_sym(id_aa64isar0_el1_sys_val); >> extern u64 kvm_nvhe_sym(id_aa64isar1_el1_sys_val); >> +extern u64 kvm_nvhe_sym(id_aa64isar2_el1_sys_val); >> extern u64 kvm_nvhe_sym(id_aa64mmfr0_el1_sys_val); >> extern u64 kvm_nvhe_sym(id_aa64mmfr1_el1_sys_val); >> extern u64 kvm_nvhe_sym(id_aa64mmfr2_el1_sys_val); >> diff --git a/arch/arm64/include/asm/sysreg.h b/arch/arm64/include/asm/sysreg.h >> index 898bee0..cbe4164 100644 >> --- a/arch/arm64/include/asm/sysreg.h >> +++ b/arch/arm64/include/asm/sysreg.h >> @@ -773,6 +773,8 @@ >> #define ID_AA64ISAR1_GPI_IMP_DEF 0x1 >> >> /* id_aa64isar2 */ >> +#define ID_AA64ISAR2_APA3_SHIFT 12 >> +#define ID_AA64ISAR2_GPA3_SHIFT 8 >> #define ID_AA64ISAR2_RPRES_SHIFT 4 >> #define ID_AA64ISAR2_WFXT_SHIFT 0 >> >> @@ -786,6 +788,16 @@ >> #define ID_AA64ISAR2_WFXT_NI 0x0 >> #define ID_AA64ISAR2_WFXT_SUPPORTED 0x2 >> >> +#define ID_AA64ISAR2_APA3_NI 0x0 >> +#define ID_AA64ISAR2_APA3_ARCHITECTED 0x1 >> +#define ID_AA64ISAR2_APA3_ARCH_EPAC 0x2 >> +#define ID_AA64ISAR2_APA3_ARCH_EPAC2 0x3 >> +#define ID_AA64ISAR2_APA3_ARCH_EPAC2_FPAC 0x4 >> +#define ID_AA64ISAR2_APA3_ARCH_EPAC2_FPAC_CMB 0x5 >> + >> +#define ID_AA64ISAR2_GPA3_NI 0x0 >> +#define ID_AA64ISAR2_GPA3_ARCHITECTED 0x1 >> + >> /* id_aa64pfr0 */ >> #define ID_AA64PFR0_CSV3_SHIFT 60 >> #define ID_AA64PFR0_CSV2_SHIFT 56 >> diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c >> index 69fbc53..aab6766 100644 >> --- a/arch/arm64/kernel/cpufeature.c >> +++ b/arch/arm64/kernel/cpufeature.c >> @@ -226,6 +226,10 @@ static const struct arm64_ftr_bits ftr_id_aa64isar1[] = { >> }; >> >> static const struct arm64_ftr_bits ftr_id_aa64isar2[] = { >> + ARM64_FTR_BITS(FTR_VISIBLE_IF_IS_ENABLED(CONFIG_ARM64_PTR_AUTH), >> + FTR_STRICT, FTR_EXACT, ID_AA64ISAR2_APA3_SHIFT, 4, 0), >> + ARM64_FTR_BITS(FTR_VISIBLE_IF_IS_ENABLED(CONFIG_ARM64_PTR_AUTH), >> + FTR_STRICT, FTR_LOWER_SAFE, ID_AA64ISAR2_GPA3_SHIFT, 4, 0), >> ARM64_FTR_BITS(FTR_VISIBLE, FTR_NONSTRICT, FTR_LOWER_SAFE, ID_AA64ISAR2_RPRES_SHIFT, 4, 0), >> ARM64_FTR_END, >> }; >> @@ -596,6 +600,7 @@ static const struct arm64_ftr_bits ftr_raz[] = { >> struct arm64_ftr_override __ro_after_init id_aa64mmfr1_override; >> struct arm64_ftr_override __ro_after_init id_aa64pfr1_override; >> struct arm64_ftr_override __ro_after_init id_aa64isar1_override; >> +struct arm64_ftr_override __ro_after_init id_aa64isar2_override; >> >> static const struct __ftr_reg_entry { >> u32 sys_id; >> @@ -644,6 +649,8 @@ static const struct __ftr_reg_entry { >> ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR1_EL1, ftr_id_aa64isar1, >> &id_aa64isar1_override), >> ARM64_FTR_REG(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2), >> + ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2, >> + &id_aa64isar2_override), >> >> /* Op1 = 0, CRn = 0, CRm = 7 */ >> ARM64_FTR_REG(SYS_ID_AA64MMFR0_EL1, ftr_id_aa64mmfr0), >> @@ -1834,10 +1841,11 @@ static bool has_address_auth_metacap(const struct arm64_cpu_capabilities *entry, >> { >> bool api = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_IMP_DEF], scope); >> bool apa = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA5], scope); >> + bool apa3 = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA3], scope); >> >> - WARN_ON(apa && api); >> + WARN_ON((apa && api) || (apa && apa3) || (api && apa3)); > > I don't really get the point in this warning, what is somebody supposed to > do if they hit it? The kernel isn't the right place to make assertions about > the CPU design. Right, there is nothing user can do other than reporting about that. It was inspired by the similar check in cpu_has_fwb(), yet I was under impression that assertion can be triggered via id regester override as well - now I see that invalid override is ignored. I'm fine with removing assertion as long as code base use assertions consistently... Cheers Vladimir > > Will > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm 2022-02-21 14:47 ` Vladimir Murzin @ 2022-02-22 21:50 ` Will Deacon 2022-02-23 11:20 ` Vladimir Murzin 0 siblings, 1 reply; 16+ messages in thread From: Will Deacon @ 2022-02-22 21:50 UTC (permalink / raw) To: Vladimir Murzin; +Cc: linux-arm-kernel, maz, catalin.marinas, mark.rutland On Mon, Feb 21, 2022 at 02:47:02PM +0000, Vladimir Murzin wrote: > On 2/15/22 6:21 PM, Will Deacon wrote: > > On Mon, Jan 31, 2022 at 05:06:54PM +0000, Vladimir Murzin wrote: > >> QARMA3 is relaxed version of the QARMA5 algorithm which expected to > >> reduce the latency of calculation while still delivering a suitable > >> level of security. > >> > >> Support for QARMA3 can be discovered via ID_AA64ISAR2_EL1 > >> > >> APA3, bits [15:12] Indicates whether the QARMA3 algorithm is > >> implemented in the PE for address > >> authentication in AArch64 state. > >> > >> GPA3, bits [11:8] Indicates whether the QARMA3 algorithm is > >> implemented in the PE for generic code > >> authentication in AArch64 state. > >> > >> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> > >> --- [...] > >> @@ -596,6 +600,7 @@ static const struct arm64_ftr_bits ftr_raz[] = { > >> struct arm64_ftr_override __ro_after_init id_aa64mmfr1_override; > >> struct arm64_ftr_override __ro_after_init id_aa64pfr1_override; > >> struct arm64_ftr_override __ro_after_init id_aa64isar1_override; > >> +struct arm64_ftr_override __ro_after_init id_aa64isar2_override; > >> > >> static const struct __ftr_reg_entry { > >> u32 sys_id; > >> @@ -644,6 +649,8 @@ static const struct __ftr_reg_entry { > >> ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR1_EL1, ftr_id_aa64isar1, > >> &id_aa64isar1_override), > >> ARM64_FTR_REG(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2), > >> + ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2, > >> + &id_aa64isar2_override), > >> > >> /* Op1 = 0, CRn = 0, CRm = 7 */ > >> ARM64_FTR_REG(SYS_ID_AA64MMFR0_EL1, ftr_id_aa64mmfr0), > >> @@ -1834,10 +1841,11 @@ static bool has_address_auth_metacap(const struct arm64_cpu_capabilities *entry, > >> { > >> bool api = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_IMP_DEF], scope); > >> bool apa = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA5], scope); > >> + bool apa3 = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA3], scope); > >> > >> - WARN_ON(apa && api); > >> + WARN_ON((apa && api) || (apa && apa3) || (api && apa3)); > > > > I don't really get the point in this warning, what is somebody supposed to > > do if they hit it? The kernel isn't the right place to make assertions about > > the CPU design. > > Right, there is nothing user can do other than reporting about that. It was > inspired by the similar check in cpu_has_fwb(), yet I was under impression > that assertion can be triggered via id regester override as well - now I see > that invalid override is ignored. I'm fine with removing assertion as long > as code base use assertions consistently... Yes, please send a version with these WARN_ON()s and I can queue it up. Cheers, Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm 2022-02-22 21:50 ` Will Deacon @ 2022-02-23 11:20 ` Vladimir Murzin 2022-02-24 9:49 ` Will Deacon 0 siblings, 1 reply; 16+ messages in thread From: Vladimir Murzin @ 2022-02-23 11:20 UTC (permalink / raw) To: Will Deacon; +Cc: linux-arm-kernel, maz, catalin.marinas, mark.rutland On 2/22/22 9:50 PM, Will Deacon wrote: > On Mon, Feb 21, 2022 at 02:47:02PM +0000, Vladimir Murzin wrote: >> On 2/15/22 6:21 PM, Will Deacon wrote: >>> On Mon, Jan 31, 2022 at 05:06:54PM +0000, Vladimir Murzin wrote: >>>> QARMA3 is relaxed version of the QARMA5 algorithm which expected to >>>> reduce the latency of calculation while still delivering a suitable >>>> level of security. >>>> >>>> Support for QARMA3 can be discovered via ID_AA64ISAR2_EL1 >>>> >>>> APA3, bits [15:12] Indicates whether the QARMA3 algorithm is >>>> implemented in the PE for address >>>> authentication in AArch64 state. >>>> >>>> GPA3, bits [11:8] Indicates whether the QARMA3 algorithm is >>>> implemented in the PE for generic code >>>> authentication in AArch64 state. >>>> >>>> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> >>>> --- > > [...] > >>>> @@ -596,6 +600,7 @@ static const struct arm64_ftr_bits ftr_raz[] = { >>>> struct arm64_ftr_override __ro_after_init id_aa64mmfr1_override; >>>> struct arm64_ftr_override __ro_after_init id_aa64pfr1_override; >>>> struct arm64_ftr_override __ro_after_init id_aa64isar1_override; >>>> +struct arm64_ftr_override __ro_after_init id_aa64isar2_override; >>>> >>>> static const struct __ftr_reg_entry { >>>> u32 sys_id; >>>> @@ -644,6 +649,8 @@ static const struct __ftr_reg_entry { >>>> ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR1_EL1, ftr_id_aa64isar1, >>>> &id_aa64isar1_override), >>>> ARM64_FTR_REG(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2), >>>> + ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2, >>>> + &id_aa64isar2_override), >>>> >>>> /* Op1 = 0, CRn = 0, CRm = 7 */ >>>> ARM64_FTR_REG(SYS_ID_AA64MMFR0_EL1, ftr_id_aa64mmfr0), >>>> @@ -1834,10 +1841,11 @@ static bool has_address_auth_metacap(const struct arm64_cpu_capabilities *entry, >>>> { >>>> bool api = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_IMP_DEF], scope); >>>> bool apa = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA5], scope); >>>> + bool apa3 = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA3], scope); >>>> >>>> - WARN_ON(apa && api); >>>> + WARN_ON((apa && api) || (apa && apa3) || (api && apa3)); >>> >>> I don't really get the point in this warning, what is somebody supposed to >>> do if they hit it? The kernel isn't the right place to make assertions about >>> the CPU design. >> >> Right, there is nothing user can do other than reporting about that. It was >> inspired by the similar check in cpu_has_fwb(), yet I was under impression >> that assertion can be triggered via id regester override as well - now I see >> that invalid override is ignored. I'm fine with removing assertion as long >> as code base use assertions consistently... > > Yes, please send a version with these WARN_ON()s and I can queue it up. ^^^^^^ Sorry, Will, did you mean *without*? Do you want separate patch to remove WARN_ON from cpu_has_fwb() as well? Cheers Vladimir > > Cheers, > > Will > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm 2022-02-23 11:20 ` Vladimir Murzin @ 2022-02-24 9:49 ` Will Deacon 0 siblings, 0 replies; 16+ messages in thread From: Will Deacon @ 2022-02-24 9:49 UTC (permalink / raw) To: Vladimir Murzin; +Cc: linux-arm-kernel, maz, catalin.marinas, mark.rutland On Wed, Feb 23, 2022 at 11:20:40AM +0000, Vladimir Murzin wrote: > On 2/22/22 9:50 PM, Will Deacon wrote: > > On Mon, Feb 21, 2022 at 02:47:02PM +0000, Vladimir Murzin wrote: > >> On 2/15/22 6:21 PM, Will Deacon wrote: > >>> On Mon, Jan 31, 2022 at 05:06:54PM +0000, Vladimir Murzin wrote: > >>>> QARMA3 is relaxed version of the QARMA5 algorithm which expected to > >>>> reduce the latency of calculation while still delivering a suitable > >>>> level of security. > >>>> > >>>> Support for QARMA3 can be discovered via ID_AA64ISAR2_EL1 > >>>> > >>>> APA3, bits [15:12] Indicates whether the QARMA3 algorithm is > >>>> implemented in the PE for address > >>>> authentication in AArch64 state. > >>>> > >>>> GPA3, bits [11:8] Indicates whether the QARMA3 algorithm is > >>>> implemented in the PE for generic code > >>>> authentication in AArch64 state. > >>>> > >>>> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> > >>>> --- > > > > [...] > > > >>>> @@ -596,6 +600,7 @@ static const struct arm64_ftr_bits ftr_raz[] = { > >>>> struct arm64_ftr_override __ro_after_init id_aa64mmfr1_override; > >>>> struct arm64_ftr_override __ro_after_init id_aa64pfr1_override; > >>>> struct arm64_ftr_override __ro_after_init id_aa64isar1_override; > >>>> +struct arm64_ftr_override __ro_after_init id_aa64isar2_override; > >>>> > >>>> static const struct __ftr_reg_entry { > >>>> u32 sys_id; > >>>> @@ -644,6 +649,8 @@ static const struct __ftr_reg_entry { > >>>> ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR1_EL1, ftr_id_aa64isar1, > >>>> &id_aa64isar1_override), > >>>> ARM64_FTR_REG(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2), > >>>> + ARM64_FTR_REG_OVERRIDE(SYS_ID_AA64ISAR2_EL1, ftr_id_aa64isar2, > >>>> + &id_aa64isar2_override), > >>>> > >>>> /* Op1 = 0, CRn = 0, CRm = 7 */ > >>>> ARM64_FTR_REG(SYS_ID_AA64MMFR0_EL1, ftr_id_aa64mmfr0), > >>>> @@ -1834,10 +1841,11 @@ static bool has_address_auth_metacap(const struct arm64_cpu_capabilities *entry, > >>>> { > >>>> bool api = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_IMP_DEF], scope); > >>>> bool apa = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA5], scope); > >>>> + bool apa3 = has_address_auth_cpucap(cpu_hwcaps_ptrs[ARM64_HAS_ADDRESS_AUTH_ARCH_QARMA3], scope); > >>>> > >>>> - WARN_ON(apa && api); > >>>> + WARN_ON((apa && api) || (apa && apa3) || (api && apa3)); > >>> > >>> I don't really get the point in this warning, what is somebody supposed to > >>> do if they hit it? The kernel isn't the right place to make assertions about > >>> the CPU design. > >> > >> Right, there is nothing user can do other than reporting about that. It was > >> inspired by the similar check in cpu_has_fwb(), yet I was under impression > >> that assertion can be triggered via id regester override as well - now I see > >> that invalid override is ignored. I'm fine with removing assertion as long > >> as code base use assertions consistently... > > > > Yes, please send a version with these WARN_ON()s and I can queue it up. > ^^^^^^ > Sorry, Will, did you mean *without*? Urgh, yes, sorry about that. > Do you want separate patch to remove WARN_ON from cpu_has_fwb() as well? Yes, good thinking. Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v2 0/4] arm64: Support of PAuth QARMA3 architected algorithm 2022-01-31 17:06 [PATCH v2 0/4] arm64: Support of PAuth QARMA3 architected algorithm Vladimir Murzin ` (3 preceding siblings ...) 2022-01-31 17:06 ` [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm Vladimir Murzin @ 2022-01-31 17:38 ` Vladimir Murzin 2022-02-05 10:27 ` Marc Zyngier 5 siblings, 0 replies; 16+ messages in thread From: Vladimir Murzin @ 2022-01-31 17:38 UTC (permalink / raw) To: linux-arm-kernel; +Cc: maz, catalin.marinas, mark.rutland, will On 1/31/22 5:06 PM, Vladimir Murzin wrote: > QARMA3 is relaxed version of the QARMA5 algorithm which expected to > reduce the latency of calculation while still delivering a suitable > level of security. > > Feature advertised via a new ID fields in ID_AA64ISAR2_EL1 [1], so we > need to teach the kernel to identify this. > > [1] https://developer.arm.com/documentation/ddi0601/2021-12/AArch64-Registers/ID-AA64ISAR2-EL1--AArch64-Instruction-Set-Attribute-Register-2?lang=en > > > Changelog: > > v1 -> v2 > - Removed unintended whitespace change in sysreg.h > - FTR_ALIAS_OPTION_LEN now accounts null terminator > - Extract only APA3 bits from ID_AA64ISAR2_APA3_SHIFT (in ^^^^^^^^^^^^^^^^^^^^^^^ should be read as ID_AA64ISAR2 > contrast to id_aa64isar1_el1 where both APA and API bits > are extracted) in asm_pointer_auth.h > > Thanks! > > Vladimir Murzin (4): > arm64: cpufeature: Account min_field_value when cheking secondaries > for PAuth > arm64: cpufeature: Warn if mutually exclusive PAuth algorithms > detected > arm64: cpufeature: Mark existing PAuth architected algorithm as QARMA5 > arm64: Add support of PAuth QARMA3 architected algorithm > > arch/arm64/include/asm/asm_pointer_auth.h | 3 ++ > arch/arm64/include/asm/cpufeature.h | 1 + > arch/arm64/include/asm/kvm_hyp.h | 1 + > arch/arm64/include/asm/sysreg.h | 12 +++++ > arch/arm64/kernel/cpufeature.c | 63 ++++++++++++++++++++++---- > arch/arm64/kernel/idreg-override.c | 16 ++++++- > arch/arm64/kvm/arm.c | 1 + > arch/arm64/kvm/hyp/include/nvhe/fixed_config.h | 5 ++ > arch/arm64/kvm/hyp/nvhe/sys_regs.c | 14 ++++++ > arch/arm64/kvm/sys_regs.c | 5 ++ > arch/arm64/tools/cpucaps | 6 ++- > 11 files changed, 114 insertions(+), 13 deletions(-) > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v2 0/4] arm64: Support of PAuth QARMA3 architected algorithm 2022-01-31 17:06 [PATCH v2 0/4] arm64: Support of PAuth QARMA3 architected algorithm Vladimir Murzin ` (4 preceding siblings ...) 2022-01-31 17:38 ` [PATCH v2 0/4] arm64: Support " Vladimir Murzin @ 2022-02-05 10:27 ` Marc Zyngier 5 siblings, 0 replies; 16+ messages in thread From: Marc Zyngier @ 2022-02-05 10:27 UTC (permalink / raw) To: Vladimir Murzin; +Cc: linux-arm-kernel, catalin.marinas, mark.rutland, will On Mon, 31 Jan 2022 17:06:50 +0000, Vladimir Murzin <vladimir.murzin@arm.com> wrote: > > QARMA3 is relaxed version of the QARMA5 algorithm which expected to > reduce the latency of calculation while still delivering a suitable > level of security. > > Feature advertised via a new ID fields in ID_AA64ISAR2_EL1 [1], so we > need to teach the kernel to identify this. > > [1] https://developer.arm.com/documentation/ddi0601/2021-12/AArch64-Registers/ID-AA64ISAR2-EL1--AArch64-Instruction-Set-Attribute-Register-2?lang=en > > > Changelog: > > v1 -> v2 > - Removed unintended whitespace change in sysreg.h > - FTR_ALIAS_OPTION_LEN now accounts null terminator > - Extract only APA3 bits from ID_AA64ISAR2_APA3_SHIFT (in > contrast to id_aa64isar1_el1 where both APA and API bits > are extracted) in asm_pointer_auth.h > > Thanks! > > Vladimir Murzin (4): > arm64: cpufeature: Account min_field_value when cheking secondaries > for PAuth > arm64: cpufeature: Warn if mutually exclusive PAuth algorithms > detected > arm64: cpufeature: Mark existing PAuth architected algorithm as QARMA5 > arm64: Add support of PAuth QARMA3 architected algorithm For the series: Reviewed-by: Marc Zyngier <maz@kernel.org> M. -- Without deviation from the norm, progress is not possible. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2022-02-24 9:51 UTC | newest] Thread overview: 16+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2022-01-31 17:06 [PATCH v2 0/4] arm64: Support of PAuth QARMA3 architected algorithm Vladimir Murzin 2022-01-31 17:06 ` [PATCH v2 1/4] arm64: cpufeature: Account min_field_value when cheking secondaries for PAuth Vladimir Murzin 2022-02-04 18:13 ` Catalin Marinas 2022-01-31 17:06 ` [PATCH v2 2/4] arm64: cpufeature: Warn if mutually exclusive PAuth algorithms detected Vladimir Murzin 2022-02-04 18:16 ` Catalin Marinas 2022-01-31 17:06 ` [PATCH v2 3/4] arm64: cpufeature: Mark existing PAuth architected algorithm as QARMA5 Vladimir Murzin 2022-02-04 18:18 ` Catalin Marinas 2022-01-31 17:06 ` [PATCH v2 4/4] arm64: Add support of PAuth QARMA3 architected algorithm Vladimir Murzin 2022-02-04 18:42 ` Catalin Marinas 2022-02-15 18:21 ` Will Deacon 2022-02-21 14:47 ` Vladimir Murzin 2022-02-22 21:50 ` Will Deacon 2022-02-23 11:20 ` Vladimir Murzin 2022-02-24 9:49 ` Will Deacon 2022-01-31 17:38 ` [PATCH v2 0/4] arm64: Support " Vladimir Murzin 2022-02-05 10:27 ` Marc Zyngier
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).