arm64/mte: Clarify mode reported by PR_GET_TAGGED_ADDR_CTRL
authorMark Brown <broonie@kernel.org>
Thu, 27 Jan 2022 19:03:23 +0000 (19:03 +0000)
committerWill Deacon <will@kernel.org>
Tue, 15 Feb 2022 16:00:09 +0000 (16:00 +0000)
commit4c022f57ad954e1ad6f838bd3b7d54e459745eeb
tree267a25c32e8746c79a67dbe82b83a7ecb3b1075f
parentb8ac4ee08d48d4bb46669a2deef10454313e1a00
arm64/mte: Clarify mode reported by PR_GET_TAGGED_ADDR_CTRL

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>
Link: https://lore.kernel.org/r/20220127190324.660405-1-broonie@kernel.org
Signed-off-by: Will Deacon <will@kernel.org>
Documentation/arm64/memory-tagging-extension.rst