From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Branislav Rankov <branislav.rankov@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] arm64/mte: Document ABI for asymmetric mode
Date: Fri, 18 Feb 2022 12:24:40 +0000 [thread overview]
Message-ID: <Yg+QCFmZ5PhZbGP6@arm.com> (raw)
In-Reply-To: <20220216173224.2342152-2-broonie@kernel.org>
On Wed, Feb 16, 2022 at 05:32:21PM +0000, Mark Brown wrote:
> To allow a program to potentially run in the CPU's preferred tag
> checking mode, the user program may set multiple tag check fault mode
> bits in the ``flags`` argument to the ``prctl(PR_SET_TAGGED_ADDR_CTRL,
> flags, 0, 0, 0)`` system call. If the CPU's preferred tag checking
> -mode is in the task's set of provided tag checking modes (this will
> -always be the case at present because the kernel only supports two
> -tag checking modes, but future kernels may support more modes), that
> +mode is in the task's set of provided tag checking modes, that
> mode will be selected. Otherwise, one of the modes in the task's mode
> -set will be selected in a currently unspecified manner.
> +selected by the kernel using the preference order:
> +
> + 1. Asynchronous
> + 2. Asymmetric
> + 3. Synchronous
> +
> +If asymmetric mode is specified by the program but not supported by
> +either the system or the kernel then an error will be returned.
This works for me.
Reviewed-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
next prev parent reply other threads:[~2022-02-18 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 17:32 [PATCH v2 0/4] arm64/mte: Asymmetric MTE support in userspace Mark Brown
2022-02-16 17:32 ` [PATCH v2 1/4] arm64/mte: Document ABI for asymmetric mode Mark Brown
2022-02-18 12:24 ` Catalin Marinas [this message]
2022-02-16 17:32 ` [PATCH v2 2/4] arm64/mte: Add a little bit of documentation for mte_update_sctlr_user() Mark Brown
2022-02-16 17:32 ` [PATCH v2 3/4] arm64/mte: Add hwcap for asymmetric mode Mark Brown
2022-02-16 17:32 ` [PATCH v2 4/4] arm64/mte: Add userspace interface for enabling " Mark Brown
2022-02-25 15:50 ` [PATCH v2 0/4] arm64/mte: Asymmetric MTE support in userspace 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=Yg+QCFmZ5PhZbGP6@arm.com \
--to=catalin.marinas@arm.com \
--cc=branislav.rankov@arm.com \
--cc=broonie@kernel.org \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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 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).