linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/mte: Clarify mode reported by PR_GET_TAGGED_ADDR_CTRL
Date: Tue, 1 Feb 2022 18:31:04 +0000	[thread overview]
Message-ID: <Yfl8aGc1QtIOJyxt@arm.com> (raw)
In-Reply-To: <20220127190324.660405-1-broonie@kernel.org>

On Thu, Jan 27, 2022 at 07:03:23PM +0000, Mark Brown wrote:
> With the current wording readers might infer that PR_GET_TAGGED_ADDR_CTRL
> will report the mode currently active in the thread however this is not the
> actual behaviour, instead all modes currently selected by the process will
> be reported with the mode used depending on the combination of the
> requested modes and the default set for the current CPU. This has been the
> case since 433c38f40f6a81 ("arm64: mte: change ASYNC and SYNC TCF settings
> into bitfields"), before that we did not allow more than one mode to be
> requested simultaneously.
> 
> Update the documentation to more clearly reflect current behaviour.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>

Acked-by: Catalin Marinas <catalin.marinas@arm.com>

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

  reply	other threads:[~2022-02-01 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 19:03 [PATCH] arm64/mte: Clarify mode reported by PR_GET_TAGGED_ADDR_CTRL Mark Brown
2022-02-01 18:31 ` Catalin Marinas [this message]
2022-02-15 23:18 ` 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=Yfl8aGc1QtIOJyxt@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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 NNTP newsgroup(s).