From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Evgenii Stepanov <eugenis@google.com>,
Branislav Rankov <Branislav.Rankov@arm.com>,
Andrey Konovalov <andreyknvl@google.com>
Subject: Re: [PATCH v3 2/4] arm64: mte: Add asynchronous mode support
Date: Sat, 16 Jan 2021 13:49:14 +0000 [thread overview]
Message-ID: <2fde5816-35a7-1e21-e42c-f6e413f30aec@arm.com> (raw)
In-Reply-To: <20210115151327.GB44111@C02TD0UTHF1T.local>
On 1/15/21 3:13 PM, Mark Rutland wrote:
> On Fri, Jan 15, 2021 at 12:00:41PM +0000, Vincenzo Frascino wrote:
>> MTE provides an asynchronous mode for detecting tag exceptions. In
>> particular instead of triggering a fault the arm64 core updates a
>> register which is checked by the kernel after the asynchronous tag
>> check fault has occurred.
>>
>> Add support for MTE asynchronous mode.
>>
>> The exception handling mechanism will be added with a future patch.
>>
>> Note: KASAN HW activates async mode via kasan.mode kernel parameter.
>> The default mode is set to synchronous.
>> The code that verifies the status of TFSR_EL1 will be added with a
>> future patch.
>>
>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>> Cc: Will Deacon <will@kernel.org>
>> Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
>> ---
>> arch/arm64/kernel/mte.c | 26 ++++++++++++++++++++++++--
>> 1 file changed, 24 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/kernel/mte.c b/arch/arm64/kernel/mte.c
>> index 53a6d734e29b..df7a1ae26d7c 100644
>> --- a/arch/arm64/kernel/mte.c
>> +++ b/arch/arm64/kernel/mte.c
>> @@ -153,8 +153,30 @@ void mte_init_tags(u64 max_tag)
>>
>> void mte_enable_kernel(enum kasan_hw_tags_mode mode)
>> {
>> - /* Enable MTE Sync Mode for EL1. */
>> - sysreg_clear_set(sctlr_el1, SCTLR_ELx_TCF_MASK, SCTLR_ELx_TCF_SYNC);
>> + const char *m;
>> +
>> + /* Preset parameter values based on the mode. */
>> + switch (mode) {
>> + case KASAN_HW_TAGS_ASYNC:
>> + /* Enable MTE Async Mode for EL1. */
>> + sysreg_clear_set(sctlr_el1, SCTLR_ELx_TCF_MASK, SCTLR_ELx_TCF_ASYNC);
>> + m = "asynchronous";
>> + break;
>> + case KASAN_HW_TAGS_SYNC:
>> + sysreg_clear_set(sctlr_el1, SCTLR_ELx_TCF_MASK, SCTLR_ELx_TCF_SYNC);
>> + m = "synchronous";
>> + break;
>> + default:
>> + /*
>> + * kasan mode should be always set hence we should
>> + * not reach this condition.
>> + */
>> + WARN_ON_ONCE(1);
>> + return;
>> + }
>> +
>> + pr_info_once("MTE: enabled in %s mode at EL1\n", m);
>> +
>> isb();
>> }
>
> For clarity, we should have that ISB before the pr_info_once().
>
Good point, I will fix it in v4.
> As with my comment on patch 1, I think with separate functions this
> would be much clearer and simpler:
>
> static inline void __mte_enable_kernel(const char *mode, unsigned long tcf)
> {
> sysreg_clear_set(sctlr_el1, SCTLR_ELx_TCF_MASK, tcf);
> isb();
>
> pr_info_once("MTE: enabled in %s mode at EL1\n", mode);
> }
>
> void mte_enable_kernel_sync(void)
> {
> __mte_enable_kernel("synchronous", SCTLR_ELx_TCF_SYNC);
> }
>
> void mte_enable_kernel_async(void)
> {
> __mte_enable_kernel("asynchronous", SCTLR_ELx_TCF_ASYNC);
> }
>
Ok, seems cleaner like this, will adapt my code accordingly.
> Thanks,
> Mark.
>
--
Regards,
Vincenzo
next prev parent reply other threads:[~2021-01-16 17:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 12:00 [PATCH v3 0/4] arm64: ARMv8.5-A: MTE: Add async " Vincenzo Frascino
2021-01-15 12:00 ` [PATCH v3 1/4] kasan, arm64: Add KASAN light mode Vincenzo Frascino
2021-01-15 15:08 ` Mark Rutland
2021-01-16 13:47 ` Vincenzo Frascino
2021-01-16 14:09 ` Andrey Konovalov
2021-01-18 10:24 ` Mark Rutland
2021-01-15 18:59 ` Andrey Konovalov
2021-01-16 13:40 ` Vincenzo Frascino
2021-01-16 13:59 ` Andrey Konovalov
2021-01-16 14:06 ` Vincenzo Frascino
2021-01-15 12:00 ` [PATCH v3 2/4] arm64: mte: Add asynchronous mode support Vincenzo Frascino
2021-01-15 15:13 ` Mark Rutland
2021-01-16 13:49 ` Vincenzo Frascino [this message]
2021-01-15 12:00 ` [PATCH v3 3/4] arm64: mte: Enable async tag check fault Vincenzo Frascino
2021-01-15 15:37 ` Mark Rutland
2021-01-18 12:57 ` Catalin Marinas
2021-01-18 13:37 ` Vincenzo Frascino
2021-01-18 14:14 ` Mark Rutland
2021-01-18 14:48 ` Vincenzo Frascino
2021-01-18 15:39 ` Vincenzo Frascino
2021-01-18 15:40 ` Vincenzo Frascino
2021-01-15 12:00 ` [PATCH v3 4/4] arm64: mte: Optimize mte_assign_mem_tag_range() Vincenzo Frascino
2021-01-15 15:45 ` Mark Rutland
2021-01-16 14:22 ` Vincenzo Frascino
2021-01-17 12:27 ` Vincenzo Frascino
2021-01-18 10:41 ` Mark Rutland
2021-01-18 11:00 ` Vincenzo Frascino
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=2fde5816-35a7-1e21-e42c-f6e413f30aec@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=Branislav.Rankov@arm.com \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@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
all inboxes | Powered by JetHome®