Received: by 2002:a05:6a10:c7c6:0:0:0:0 with SMTP id h6csp1717776pxy; Mon, 2 Aug 2021 08:33:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwnTh5uR0f4rmeHE3SQgayP63eLkapPpQjx7k0r3ysrBsu68qtQed2dMAmF2AojOWaYNd1S X-Received: by 2002:a17:906:cec1:: with SMTP id si1mr11616019ejb.524.1627918438441; Mon, 02 Aug 2021 08:33:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627918438; cv=none; d=google.com; s=arc-20160816; b=ueQsfa4L0PQlGjM0+pSkLOtEU9ZPFe06v8nm/Xq+5QKp+72/JwCuK9hzcUMS5uhdAl 6jVsz6a8mzT7ZkGlt//pZeOnLDaHPybI0iGxpWaoduXoKgGbh+oCRza7H5URH2Hx0Ty+ zcF1V36bBD0mRCZrAXrpttRIy2QfO3TH9lKOa2MchQ1J1tnfTGaHbS2qnlDUfL9WSCiU Bn6dyjPSkE5rg54vL0voXxrQdHUBgFNL4ZfY8oujTqTAHxeQaEuWxDJgQQkDKzDwNfTN 2v5XI8CHxh9xG4mKVSa7wsMRKPYFRio5v/D8WWLa5Yd8Ba9IyKtKdm5LbXcV2+t+uKLl BxPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=o1czmpIZsUKOBYK3IeH2vhknFViRz6ZAb/WUkML/vw0=; b=SDMiPoBCVxmRBgVyCCqJphMs4ElPUEyUlKTl6/4Vk15smxqpEpg1Be9wUvZ83WZXgJ QSHwiXKIizFgCscmYlHU+icTqaGMpkr4yVCGq0NjLwSPZJescdE3mPPDshmD15xdVA1K OCVInwxWVWMv+ePEEAKQ+9pb/VtlvG7zutyDU/os103gL9GAmb9AMCp3VeTnHDU1TUpr xw6JUtH/JAh6scviVlWhlGARhId6crOgppf/tnWTA2qPUQoOvbgcmaiOvm7B81JSZUHa EQ7O4+S+2ONYJmxhhI497oLGwGjHaUiM8M2tFDh8zNdsAn/qu0Li4i+FQ130wzl1WADl 5zVA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u2si10649129edq.316.2021.08.02.08.33.33; Mon, 02 Aug 2021 08:33:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235187AbhHBPay (ORCPT + 99 others); Mon, 2 Aug 2021 11:30:54 -0400 Received: from mail.kernel.org ([198.145.29.99]:42634 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235164AbhHBPax (ORCPT ); Mon, 2 Aug 2021 11:30:53 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 7607461103; Mon, 2 Aug 2021 15:30:40 +0000 (UTC) Date: Mon, 2 Aug 2021 16:30:37 +0100 From: Catalin Marinas To: yee.lee@mediatek.com Cc: linux-kernel@vger.kernel.org, nicholas.Tang@mediatek.com, Kuan-Ying.lee@mediatek.com, chinwen.chang@mediatek.com, Jonathan Corbet , Will Deacon , Matthias Brugger , "Paul E. McKenney" , Randy Dunlap , Andrew Morton , Thomas Gleixner , "Maciej W. Rozycki" , Viresh Kumar , Peter Zijlstra , Vlastimil Babka , Marc Zyngier , David Brazdil , Ard Biesheuvel , Fuad Tabba , "open list:DOCUMENTATION" , "moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)" , "moderated list:ARM/Mediatek SoC support" Subject: Re: [PATCH v3 1/1] arm64/cpufeature: Optionally disable MTE via command-line Message-ID: <20210802153036.GH18685@arm.com> References: <20210730144957.30938-1-yee.lee@mediatek.com> <20210730144957.30938-2-yee.lee@mediatek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210730144957.30938-2-yee.lee@mediatek.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 30, 2021 at 10:49:53PM +0800, yee.lee@mediatek.com wrote: > From: Yee Lee > > For some low-end devices with limited resources, > MTE needs to be optionally disabled to save system > costs such as tag memory and firmware controls. I understand the cost of using MTE but I don't fully get what you mean by firmware controls. If the ID_AA64PFR1_EL1.MTE reports that MTE is present, the firmware should have initialised MTE correctly (e.g. tag allocation storage, SCR_EL3.ATA) and not rely on a kernel command line argument that may or may not be present. > This allows ID_AA64PFR1_EL1.MTE to be overridden on > its shadow value by giving "arm64.nomte" on cmdline, > and to suppress MTE feature. > > Suggested-by: Marc Zyngier > Suggested-by: Suzuki K Poulose > Signed-off-by: Yee Lee While this patch appears to disable MTE, I don't think it can fully prevent the access to the allocation tag storage, so the firmware must still initialise it correctly. The issue is that __cpu_setup already configures the MAIR_EL1 register to use Normal Tagged memory for the kernel mapping and SCTLR_EL1.ATA is set. The TCF field is zero, so no tag checking, but I couldn't figure out from the ARM ARM whether this also prevents LDR/STR from attempting to fetch the allocation tags. I think it's only the ATA bit and the MAIR configuration. With this patch, KASAN_HW_TAGS (if configured) won't be used and MTE will not be presented to user applications, if that's what you want, but does not fully disable MTE. Since May this year, the ARM ARM was updated so that SCTLR_EL1.ATA/ATA0 are not permitted to be cached in the TLB. We could therefore move the setting to cpu_enable_mte(). Something like below, untested (to be folded into your patch): diff --git a/arch/arm64/include/asm/sysreg.h b/arch/arm64/include/asm/sysreg.h index aa53954c2f6b..cac23455a2b5 100644 --- a/arch/arm64/include/asm/sysreg.h +++ b/arch/arm64/include/asm/sysreg.h @@ -698,8 +698,7 @@ (SCTLR_ELx_M | SCTLR_ELx_C | SCTLR_ELx_SA | SCTLR_EL1_SA0 | \ SCTLR_EL1_SED | SCTLR_ELx_I | SCTLR_EL1_DZE | SCTLR_EL1_UCT | \ SCTLR_EL1_NTWE | SCTLR_ELx_IESB | SCTLR_EL1_SPAN | SCTLR_ELx_ITFSB | \ - SCTLR_ELx_ATA | SCTLR_EL1_ATA0 | ENDIAN_SET_EL1 | SCTLR_EL1_UCI | \ - SCTLR_EL1_EPAN | SCTLR_EL1_RES1) + ENDIAN_SET_EL1 | SCTLR_EL1_UCI | SCTLR_EL1_EPAN | SCTLR_EL1_RES1) /* MAIR_ELx memory attributes (used by Linux) */ #define MAIR_ATTR_DEVICE_nGnRnE UL(0x00) diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c index 9035c367d08b..23b1e3d83603 100644 --- a/arch/arm64/kernel/cpufeature.c +++ b/arch/arm64/kernel/cpufeature.c @@ -1841,6 +1841,9 @@ static void bti_enable(const struct arm64_cpu_capabilities *__unused) #ifdef CONFIG_ARM64_MTE static void cpu_enable_mte(struct arm64_cpu_capabilities const *cap) { + sysreg_clear_set(sctlr_el1, 0, SCTLR_ELx_ATA | SCTLR_EL1_ATA0); + isb(); + /* * Clear the tags in the zero page. This needs to be done via the * linear map which has the Tagged attribute. -- Catalin