From: Catalin Marinas <catalin.marinas@arm.com>
To: Peter Collingbourne <pcc@google.com>
Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>,
Will Deacon <will@kernel.org>,
Evgenii Stepanov <eugenis@google.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Tejas Belagod <Tejas.Belagod@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 0/4] arm64: mte: allow async MTE to be upgraded to sync on a per-CPU basis
Date: Thu, 1 Jul 2021 18:10:14 +0100 [thread overview]
Message-ID: <20210701171014.GH12484@arm.com> (raw)
In-Reply-To: <20210630231509.3773172-1-pcc@google.com>
On Wed, Jun 30, 2021 at 04:15:05PM -0700, Peter Collingbourne wrote:
> On some CPUs the performance of MTE in synchronous mode is similar
> to that of asynchronous mode. This makes it worthwhile to enable
> synchronous mode on those CPUs when asynchronous mode is requested,
> in order to gain the error detection benefits of synchronous mode
> without the performance downsides. Therefore, make it possible for
> user programs to opt into upgrading to synchronous mode on those CPUs.
>
> This is done by introducing a notion of a preferred TCF mode, which is
> controlled on a per-CPU basis by a sysfs node. The existing SYNC and
> ASYNC TCF settings are repurposed as bitfields that specify a set of
> possible modes. If the preferred TCF mode for a particular CPU is in
> the user-provided mode set (this will always be the case for mode sets
> containing more than one mode because the kernel only supports two tag
> checking modes, but future kernels may support more modes) then that
> mode is used when running on that CPU, otherwise one of the modes in
> the task's mode set will be selected in a currently unspecified manner.
The series looks good to me but please post it again after -rc1 if it
doesn't apply cleanly.
Thanks.
--
Catalin
_______________________________________________
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:[~2021-07-01 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 23:15 [PATCH v8 0/4] arm64: mte: allow async MTE to be upgraded to sync on a per-CPU basis Peter Collingbourne
2021-06-30 23:15 ` [PATCH v8 1/4] arm64: mte: rename gcr_user_excl to mte_ctrl Peter Collingbourne
2021-07-01 17:06 ` Catalin Marinas
2021-06-30 23:15 ` [PATCH v8 2/4] arm64: mte: change ASYNC and SYNC TCF settings into bitfields Peter Collingbourne
2021-07-01 17:07 ` Catalin Marinas
2021-06-30 23:15 ` [PATCH v8 3/4] arm64: mte: introduce a per-CPU tag checking mode preference Peter Collingbourne
2021-07-01 17:09 ` Catalin Marinas
2021-06-30 23:15 ` [PATCH v8 4/4] Documentation: document the preferred tag checking mode feature Peter Collingbourne
2021-07-01 17:04 ` Catalin Marinas
2021-07-01 17:09 ` Catalin Marinas
2021-07-01 17:10 ` Catalin Marinas [this message]
2021-07-02 19:42 ` [PATCH v8 0/4] arm64: mte: allow async MTE to be upgraded to sync on a per-CPU basis 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=20210701171014.GH12484@arm.com \
--to=catalin.marinas@arm.com \
--cc=Tejas.Belagod@arm.com \
--cc=eugenis@google.com \
--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 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.