From: Catalin Marinas <email@example.com>
To: Peter Collingbourne <firstname.lastname@example.org>
Cc: Vincenzo Frascino <email@example.com>,
Will Deacon <firstname.lastname@example.org>,
Evgenii Stepanov <email@example.com>,
Subject: Re: [PATCH] arm64: mte: allow async MTE to be upgraded to sync on a per-CPU basis
Date: Thu, 3 Jun 2021 15:30:21 +0100 [thread overview]
Message-ID: <20210603143020.GD20338@arm.com> (raw)
On Wed, Jun 02, 2021 at 04:24:45PM -0700, Peter Collingbourne wrote:
> On some CPUs the performance of MTE in synchronous mode is the same
> as 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 CPUs
> to opt into upgrading to synchronous mode via a new mte-prefer-sync
> device tree attribute.
As Vincenzo said, there's an ABI change which I don't particularly like.
I think the current PR_MTE_TCF_* should be honoured as they described.
We could introduce a new control, PR_MTE_TCF_DYNAMIC (or a better name)
that would cover both your mixed system or some future scenario where we
want to switch between async and sync (and the new asymmetric mode in
8.7) at run-time via some other control/timer and transparently from the
application. But that would be an application opt-in.
linux-arm-kernel mailing list
prev parent reply other threads:[~2021-06-03 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 23:24 [PATCH] arm64: mte: allow async MTE to be upgraded to sync on a per-CPU basis Peter Collingbourne
2021-06-03 13:02 ` Vincenzo Frascino
2021-06-03 17:49 ` Peter Collingbourne
2021-06-08 14:43 ` Catalin Marinas
2021-06-08 19:54 ` Peter Collingbourne
2021-06-08 21:55 ` Evgenii Stepanov
2021-06-03 14:30 ` Catalin Marinas [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.