From: Marc Zyngier <maz@kernel.org>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
mark.rutland@arm.com, will@kernel.org
Subject: Re: [PATCH v3 0/3] arm64: Support of PAuth QARMA3 architected algorithm
Date: Thu, 24 Feb 2022 15:18:44 +0000 [thread overview]
Message-ID: <0e3614c72b6fbb235258c65b4b9c65c2@kernel.org> (raw)
In-Reply-To: <20220224124952.119612-1-vladimir.murzin@arm.com>
On 2022-02-24 12:49, 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
> contrast to id_aa64isar1_el1 where both APA and API bits
> are extracted) in asm_pointer_auth.h
> v2 -> v3
> - Removed WARN_ON(s) (per Will)
> - Rebased on 5.17-rc5
>
> Thanks!
>
> Vladimir Murzin (3):
> arm64: cpufeature: Account min_field_value when cheking secondaries
> for PAuth
> 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 | 59
> ++++++++++++++++++++++----
> 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, 110 insertions(+), 13 deletions(-)
For the series:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
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:[~2022-02-24 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 12:49 [PATCH v3 0/3] arm64: Support of PAuth QARMA3 architected algorithm Vladimir Murzin
2022-02-24 12:49 ` [PATCH v3 1/3] arm64: cpufeature: Account min_field_value when cheking secondaries for PAuth Vladimir Murzin
2022-02-24 12:49 ` [PATCH v3 2/3] arm64: cpufeature: Mark existing PAuth architected algorithm as QARMA5 Vladimir Murzin
2022-02-24 12:49 ` [PATCH v3 3/3] arm64: Add support of PAuth QARMA3 architected algorithm Vladimir Murzin
2022-02-24 15:18 ` Marc Zyngier [this message]
2022-02-25 15:50 ` [PATCH v3 0/3] arm64: Support " Will Deacon
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=0e3614c72b6fbb235258c65b4b9c65c2@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=vladimir.murzin@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;
as well as URLs for NNTP newsgroup(s).