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:     Mark Brown <broonie@kernel.org>,
        Peter Collingbourne <pcc@google.com>,
        Jonathan Corbet <corbet@lwn.net>, Will Deacon <will@kernel.org>
Cc:     linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: document the boot requirements for MTE
Date:   Mon, 25 Apr 2022 17:19:58 +0100
Message-Id: <165090359492.2745002.14281951356771675020.b4-ty@arm.com>
In-Reply-To: <20220422202912.292039-1-pcc@google.com>
References: <20220422202912.292039-1-pcc@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 22 Apr 2022 13:29:12 -0700, Peter Collingbourne wrote:
> When booting the kernel we access system registers such as GCR_EL1
> if MTE is supported. These accesses are defined to trap to EL3 if
> SCR_EL3.ATA is disabled. Furthermore, tag accesses will not behave
> as expected if SCR_EL3.ATA is not set, or if HCR_EL2.ATA is not set
> and we were booted at EL1. Therefore, require that these bits are
> enabled when appropriate.
> 
> [...]

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

[1/1] arm64: document the boot requirements for MTE
      https://git.kernel.org/arm64/c/b6ba1a89f73f

-- 
Catalin