All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Peter Collingbourne <pcc@google.com>,
	Will Deacon <will@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Szabolcs Nagy <szabolcs.nagy@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	Tejas Belagod <Tejas.Belagod@arm.com>,
	Evgenii Stepanov <eugenis@google.com>
Subject: Re: [PATCH v11 0/5] arm64: mte: allow async MTE to be upgraded to sync on a per-CPU basis
Date: Wed, 28 Jul 2021 18:46:15 +0100	[thread overview]
Message-ID: <162749406642.26134.16808284983239195005.b4-ty@arm.com> (raw)
In-Reply-To: <20210727205300.2554659-1-pcc@google.com>

On Tue, 27 Jul 2021 13:52:54 -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.
> 
> [...]

Applied to arm64 (for-next/mte) but first added Will's acks from v10 an
changed the Documentation/ patch to state "when scheduling" instead of
"when running". Thanks!

[1/5] arm64: mte: rename gcr_user_excl to mte_ctrl
      https://git.kernel.org/arm64/c/638982a03fbc
[2/5] arm64: mte: change ASYNC and SYNC TCF settings into bitfields
      https://git.kernel.org/arm64/c/433c38f40f6a
[3/5] arm64: move preemption disablement to prctl handlers
      https://git.kernel.org/arm64/c/d2e0d8f9746d
[4/5] arm64: mte: introduce a per-CPU tag checking mode preference
      https://git.kernel.org/arm64/c/dd061616edcf
[5/5] Documentation: document the preferred tag checking mode feature
      https://git.kernel.org/arm64/c/80c7c36fb3dd

-- 
Catalin


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2021-07-28 17:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 20:52 [PATCH v11 0/5] arm64: mte: allow async MTE to be upgraded to sync on a per-CPU basis Peter Collingbourne
2021-07-27 20:52 ` [PATCH v11 1/5] arm64: mte: rename gcr_user_excl to mte_ctrl Peter Collingbourne
2021-07-27 20:52 ` [PATCH v11 2/5] arm64: mte: change ASYNC and SYNC TCF settings into bitfields Peter Collingbourne
2021-07-27 20:52 ` [PATCH v11 3/5] arm64: move preemption disablement to prctl handlers Peter Collingbourne
2021-07-27 20:52 ` [PATCH v11 4/5] arm64: mte: introduce a per-CPU tag checking mode preference Peter Collingbourne
2021-07-27 20:52 ` [PATCH v11 5/5] Documentation: document the preferred tag checking mode feature Peter Collingbourne
2021-07-28  6:11   ` Greg Kroah-Hartman
2021-07-28 17:38     ` Catalin Marinas
2021-07-28 17:46 ` Catalin Marinas [this message]

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=162749406642.26134.16808284983239195005.b4-ty@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=Tejas.Belagod@arm.com \
    --cc=eugenis@google.com \
    --cc=gregkh@linuxfoundation.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 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.