From: Catalin Marinas <catalin.marinas@arm.com>
To: Florian Weimer <fw@deneb.enyo.de>,
Evgenii Stepanov <eugenis@google.com>,
Kostya Serebryany <kcc@google.com>,
Dave Martin <Dave.Martin@arm.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Peter Collingbourne <pcc@google.com>
Cc: Will Deacon <will@kernel.org>,
linux-api@vger.kernel.org, libc-alpha@sourceware.org,
Andrey Konovalov <andreyknvl@google.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Kevin Brodsky <kevin.brodsky@arm.com>
Subject: Re: [PATCH v4 1/2] arm64: mte: make the per-task SCTLR_EL1 field usable elsewhere
Date: Fri, 27 Nov 2020 19:13:43 +0000 [thread overview]
Message-ID: <160650438443.22092.12368244632759393865.b4-ty@arm.com> (raw)
In-Reply-To: <b584bf342a38580daa7aa73eda72184e9453a5e4.1605842067.git.pcc@google.com>
On Thu, 19 Nov 2020 19:29:46 -0800, Peter Collingbourne wrote:
> In an upcoming change we are going to introduce per-task SCTLR_EL1
> bits for PAC. Move the existing per-task SCTLR_EL1 field out of the
> MTE-specific code so that we will be able to use it from both the
> PAC and MTE code paths and make the task switching code more efficient.
Applied to arm64 (for-next/pac-keys-ctrl), thanks!
[1/2] arm64: mte: make the per-task SCTLR_EL1 field usable elsewhere
https://git.kernel.org/arm64/c/e710c29e0177
[2/2] arm64: Introduce prctl(PR_PAC_{SET,GET}_ENABLED_KEYS)
https://git.kernel.org/arm64/c/284c64e9eba3
If Dave has any other comments next week, we can apply them on top.
--
Catalin
next prev parent reply other threads:[~2020-11-27 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 3:29 Peter Collingbourne
2020-11-20 3:29 ` [PATCH v4 2/2] arm64: Introduce prctl(PR_PAC_{SET,GET}_ENABLED_KEYS) Peter Collingbourne
2020-11-27 19:13 ` Catalin Marinas [this message]
2020-11-30 12:51 ` [PATCH v4 1/2] arm64: mte: make the per-task SCTLR_EL1 field usable elsewhere Catalin Marinas
2020-12-03 8:58 ` Peter Collingbourne
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=160650438443.22092.12368244632759393865.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=Dave.Martin@arm.com \
--cc=andreyknvl@google.com \
--cc=eugenis@google.com \
--cc=fw@deneb.enyo.de \
--cc=kcc@google.com \
--cc=kevin.brodsky@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=pcc@google.com \
--cc=szabolcs.nagy@arm.com \
--cc=vincenzo.frascino@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 read-only IMAP folder(s) and NNTP newsgroup(s).