From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id C68EF3839A1 for ; Mon, 3 Aug 2026 03:52:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785729132; cv=none; b=ppyVpKpohvlUHJDN6MRv9+xpbJj7W/2YDvk62BB1xnJj2VldCNuGmUyvnEmcCq27HyXOmc3T8Z11bvjx9BR1Z2DUjJmjjfcGQf7iIQxKuElz/0h4s9MSERZ4Eco2Fujg92w3mW84H2lmqLsKCUmf9j2cDBq4YS3FMH+8aAIztP8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785729132; c=relaxed/simple; bh=MMvyCXZogY5GexaFnJZNjm1E8eW84bXx4Pe82k6Fhu0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=gzXYUGZTpatDEd+nmLffDEiG9DcnayvxWko8XvQLzDtweDUo3eGq83aQWQgV2ytuSJxwTmuySFh2m2vwcOcEYxfSkFUrE7antNanlUOaTxImNbSAngP/IHxHGYoJB3ssyLPo5R+htx1XpQotOh7y9y+hJw178uqawncvnoYAMT4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; dkim=pass (1024-bit key) header.d=arm.com header.i=@arm.com header.b=cncpuTcY; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=arm.com header.i=@arm.com header.b="cncpuTcY" Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 643D51476; Sun, 2 Aug 2026 20:52:02 -0700 (PDT) Received: from localhost (a079125.arm.com [10.164.21.43]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B27843F86F; Sun, 2 Aug 2026 20:52:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arm.com; s=foss; t=1785729126; bh=MMvyCXZogY5GexaFnJZNjm1E8eW84bXx4Pe82k6Fhu0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=cncpuTcYd1zhdHDbpXR+M48JeVJjbcQwqQJtN3m16OAM3/sYUVtu8hitSOD1ZfChq YLLRP/lYPDcOAfFhjiM35VwcFnTHoRxAqJaKggt+tDGGOdtP55CN3eGukND2rpcFX/ hyHKYlDsFImfqRAgVSWRn1uigQUVAZgc9Bv288hE= Date: Mon, 3 Aug 2026 09:22:02 +0530 From: Linu Cherian To: Will Deacon Cc: Catalin Marinas , Ryan Roberts , Kevin Brodsky , Anshuman Khandual , Suzuki K Poulose , Mark Rutland , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Gavin Shan Subject: Re: [PATCH v4 6/6] arm64: cpufeature: Detect BBML3 based on ID_AA64MMFR2_EL1.BBM Message-ID: References: <20260723044034.2983651-1-linu.cherian@arm.com> <20260723044034.2983651-7-linu.cherian@arm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Hi Will, On Fri, Jul 31, 2026 at 04:13:20PM +0100, Will Deacon wrote: > On Thu, Jul 23, 2026 at 10:10:33AM +0530, Linu Cherian wrote: > > Add ID_AA64MMFR2_EL1.BBM based BBML3 feature detection in > > cpu_supports_bbml3() so that cpus with the feature would > > not have to be added into MIDR based supports_bbml3_list. > > > > Reviewed-by: Gavin Shan > > Reviewed-by: Anshuman Khandual > > Signed-off-by: Linu Cherian > > --- > > arch/arm64/kernel/cpufeature.c | 17 +++++++++-------- > > 1 file changed, 9 insertions(+), 8 deletions(-) > > > > diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c > > index 896bafdb00b1..dbd7d187520c 100644 > > --- a/arch/arm64/kernel/cpufeature.c > > +++ b/arch/arm64/kernel/cpufeature.c > > @@ -2133,6 +2133,12 @@ static bool hvhe_possible(const struct arm64_cpu_capabilities *entry, > > > > bool cpu_supports_bbml3(void) > > { > > + u64 mmfr2; > > + > > + mmfr2 = __read_sysreg_by_encoding(SYS_ID_AA64MMFR2_EL1); > > + if (SYS_FIELD_GET(ID_AA64MMFR2_EL1, BBM, mmfr2) >= ID_AA64MMFR2_EL1_BBM_3) > > + return true; > > This is a bit of a nit, but I think it would be more consistent to use > has_cpuid_feature() here instead of __read_sysreg_by_encoding(), similarly > to how we handle kpti in unmap_kernel_at_el0() (which also has both an > ID register field and a list of MIDRs). force_pte_mapping required by map_mem(during early boot) needs cpu_supports_bbml3 check and cpu features/capabilities are not initialized by that time. Should i add a comment there to clarify this ? Thanks, Linu Cherian.