Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753877AbdLMVbN (ORCPT ); Wed, 13 Dec 2017 16:31:13 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:42712 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753744AbdLMVbK (ORCPT ); Wed, 13 Dec 2017 16:31:10 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org E365360A04 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=sboyd@codeaurora.org Date: Wed, 13 Dec 2017 13:31:08 -0800 From: Stephen Boyd To: Will Deacon Cc: Catalin Marinas , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2] arm64: cpu_errata: Add Kryo to Falkor 1003 errata Message-ID: <20171213213108.GM7997@codeaurora.org> References: <20171129230353.11809-1-sboyd@codeaurora.org> <20171212181156.GA25244@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171212181156.GA25244@arm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1477 Lines: 34 On 12/12, Will Deacon wrote: > Hi Stephen, > > On Wed, Nov 29, 2017 at 03:03:53PM -0800, Stephen Boyd wrote: > > The Kryo CPUs are also affected by the Falkor 1003 errata, so > > we need to do the same workaround on Kryo CPUs. The MIDR is > > slightly more complicated here, where the PART number is not > > always the same when looking at all the bits from 15 to 4. Drop > > the lower 8 bits and just look at the top 4 to see if it's '2' > > and then consider those as Kryo CPUs. This covers all the > > combinations without having to list them all out. > > > > Introduce a new hardware cap bit for the combination of hardware > > PAN support and this errata so that we can disable support for > > software PAN at runtime if this errata is present and the CPU > > doesn't support HW PAN. This happens on some Kryo CPUs where the > > HW PAN feature isn't supported but we can't prevent software PAN > > from being selected in the configuration. Previously, Falkor CPUs > > were all known to have HW PAN support, so we didn't need to worry > > about this case. > > > > Fixes: 38fd94b0275c ("arm64: Work around Falkor erratum 1003") > > Signed-off-by: Stephen Boyd > > --- > > Can you respin this on top of for-next/core please? The PAN bits should > be much simpler with the KPTI code. > No problem. I'll send it out in a couple hours. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project