From: Daniel Kiss <daniel.kiss@arm.com>
To: daniel.kiss@arm.com
Cc: Catalin.Marinas@arm.com, will@kernel.org, pcc@google.com,
Ard.Biesheuvel@arm.com, linux-arm-kernel@lists.infradead.org
Subject: arm64: split ARM64_PTR_AUTH option to userspace and kernel
Date: Fri, 18 Dec 2020 12:56:30 +0100 [thread overview]
Message-ID: <20201218115632.59067-1-daniel.kiss@arm.com> (raw)
In-Reply-To: <26513330-006C-4B28-9123-656CAEB70E1A@arm.com>
As discussed the A-key left enabled, this makes the patch simpler too.
arch/arm64/crypto/poly1305-core.S_shipped contains PACISP/AUTISP
instructions but this code is called while the preeption is disabled,
therefore it won't cause any trouble.
v2:
- dropped the keychange/enablement for the kernel keys.
_______________________________________________
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:[~2020-12-18 11:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 22:46 arm64: split ARM64_PTR_AUTH option to userspace and kernel configs Daniel Kiss
2020-12-07 22:46 ` [PATCH 1/2] arm64: Add ARM64_PTR_AUTH_KERNEL config option Daniel Kiss
2020-12-07 22:46 ` [PATCH 2/2] arm64: Configure kernel's PTR_AUTH key when it is built with PTR_AUTH Daniel Kiss
2020-12-07 23:07 ` Peter Collingbourne
2020-12-08 11:00 ` Catalin Marinas
2020-12-08 19:33 ` Peter Collingbourne
2020-12-09 10:51 ` Will Deacon
2020-12-09 11:56 ` Daniel Kiss
2020-12-18 11:56 ` Daniel Kiss [this message]
2020-12-18 11:56 ` [PATCH v2 1/2] arm64: Add ARM64_PTR_AUTH_KERNEL config option Daniel Kiss
2021-01-26 13:27 ` Will Deacon
2021-02-08 14:39 ` Daniel Kiss
2020-12-18 11:56 ` [PATCH v2 2/2] arm64: Do not configure kernel's PTR_AUTH key when it not needed Daniel Kiss
2021-01-26 13:32 ` Will Deacon
2021-01-26 13:17 ` arm64: split ARM64_PTR_AUTH option to userspace and kernel 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=20201218115632.59067-1-daniel.kiss@arm.com \
--to=daniel.kiss@arm.com \
--cc=Ard.Biesheuvel@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=pcc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.