Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Catalin Marinas <catalin.marinas@arm.com>
To:     Evgenii Stepanov <eugenis@google.com>,
        Peter Collingbourne <pcc@google.com>
Cc:     Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
        Kenny Root <kroot@google.com>, Mark Brown <broonie@kernel.org>,
        Andrey Konovalov <andreyknvl@gmail.com>,
        Vincenzo Frascino <vincenzo.frascino@arm.com>,
        LKML <linux-kernel@vger.kernel.org>,
        kernel test robot <lkp@intel.com>, stable@vger.kernel.org,
        Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5] arm64: mte: move register initialization to C
Date:   Thu, 22 Sep 2022 21:01:37 +0100
Message-Id: <166387689171.428844.17569339789321559720.b4-ty@arm.com>
In-Reply-To: <20220915222053.3484231-1-eugenis@google.com>
References: <20220915222053.3484231-1-eugenis@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 15 Sep 2022 15:20:53 -0700, Evgenii Stepanov wrote:
> From: Peter Collingbourne <pcc@google.com>
> 
> If FEAT_MTE2 is disabled via the arm64.nomte command line argument on a
> CPU that claims to support FEAT_MTE2, the kernel will use Tagged Normal
> in the MAIR. If we interpret arm64.nomte to mean that the CPU does not
> in fact implement FEAT_MTE2, setting the system register like this may
> lead to UNSPECIFIED behavior. Fix it by arranging for MAIR to be set
> in the C function cpu_enable_mte which is called based on the sanitized
> version of the system register.
> 
> [...]

Applied to arm64 (for-next/misc), thanks!

[1/1] arm64: mte: move register initialization to C
      https://git.kernel.org/arm64/c/973b9e373306

-- 
Catalin