Received: by 10.223.176.5 with SMTP id f5csp1766004wra; Thu, 8 Feb 2018 03:09:22 -0800 (PST) X-Google-Smtp-Source: AH8x226mG5QtdbOEODYnSme/IzfuNeFAL2YVP9SRrxwUMvCX6/8MZduIfm+Sg2ffN2WfPgtJ4DO1 X-Received: by 10.99.123.25 with SMTP id w25mr229947pgc.305.1518088162455; Thu, 08 Feb 2018 03:09:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518088162; cv=none; d=google.com; s=arc-20160816; b=AEsHtaO9APwIlotfbGWmoZancU1cV2iblZSvObbHAo8cQ4G/wJOmbfYQq2i+D0TGD8 ZCIrCdOyoV53dzTXrJHc4LLYdkACFq7c/LGYTzZ7D6+iSxxPnRYPwvdGZ8qXKKZ2L/Ry M6l0WUl7VesSyHqaUWqSTP3OnSlab3vTTeJWvN5/l74PON59k8ZIdNJwwRM12BM3aVdH nz5aVCqBgXd9JhHi6PPEKoW2ofQUJSq0pmi91EFMeYBBH37LfXvMeu4d17Zt+iJPcFvK wLubiBkFnHa0P6foEeNlfNbRFbSDSItpTljxGt9IYPu8Jz3byiFfp3XQfLTnlDEd9XV+ lBWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=VOIaqPpAt1qhOZhpJk+tc7ax26WGs9CZutt0hJyFwdo=; b=Ze02xoGBjzs02xAzLsoqZfTVqdSXDdD27D1GC54IZA+2tu2PEKiHUVx0Lyy/igBn+T J+qd4wgXTGhNFOO6583Jy3dkxOvtk6HmkjAHXNMANq+lruJoYjqb4JbA/Qd/d5Z/jSyH x+NWwvavQoOr/0iCGN3Gq33T+38cMsIy7G7/NnMh7yS3bWHn6uZBSPqwW9+Y1+Y5tidH KiJ7eTYNBDzC34oH9bwMbGKFxMg6/lgWlezKj5qYWH3uQ6C74WnT8kWDkomBnO+5CZgs TdkjvDfaV/yf3GmQrODVzR1tRLBvAyyLjtmNYoZHMq86rkIMWdVh7XxC2Md69psXoj5w VAOw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b24si2585371pfd.321.2018.02.08.03.09.08; Thu, 08 Feb 2018 03:09:22 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752210AbeBHLIX (ORCPT + 99 others); Thu, 8 Feb 2018 06:08:23 -0500 Received: from foss.arm.com ([217.140.101.70]:33122 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751995AbeBHLIW (ORCPT ); Thu, 8 Feb 2018 06:08:22 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id EC0EB80D; Thu, 8 Feb 2018 03:08:21 -0800 (PST) Received: from [10.1.206.28] (e107814-lin.cambridge.arm.com [10.1.206.28]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id AD05C3F24D; Thu, 8 Feb 2018 03:08:19 -0800 (PST) Subject: Re: [PATCH v1 05/16] arm64: Helper for parange to PASize To: Christoffer Dall Cc: linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu, marc.zyngier@arm.com, linux-kernel@vger.kernel.org, kristina.martsenko@arm.com, peter.maydell@linaro.org, pbonzini@redhat.com, rkrcmar@redhat.com, will.deacon@arm.com, ard.biesheuvel@linaro.org, mark.rutland@arm.com, catalin.marinas@arm.com References: <20180109190414.4017-1-suzuki.poulose@arm.com> <20180109190414.4017-6-suzuki.poulose@arm.com> <20180208110042.GH29286@cbox> From: Suzuki K Poulose Message-ID: <040b00f2-3e83-a475-ae20-5e9358fc580a@arm.com> Date: Thu, 8 Feb 2018 11:08:18 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180208110042.GH29286@cbox> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/02/18 11:00, Christoffer Dall wrote: > On Tue, Jan 09, 2018 at 07:04:00PM +0000, Suzuki K Poulose wrote: >> Add a helper to convert ID_AA64MMFR0_EL1:PARange to they physical > *the* >> size shift. Limit the size to the maximum supported by the kernel. > > Is this just a cleanup or are we actually going to need this feature in > the subsequent patches? That would be nice to motivate in the commit > letter. It is a cleanup, plus we are going to move the user of the code around from one place to the other. So this makes it a bit easier and cleaner. >> >> Cc: Mark Rutland >> Cc: Catalin Marinas >> Cc: Will Deacon >> Cc: Marc Zyngier >> Signed-off-by: Suzuki K Poulose >> --- >> arch/arm64/include/asm/cpufeature.h | 16 ++++++++++++++++ >> arch/arm64/kvm/hyp/s2-setup.c | 28 +++++----------------------- >> 2 files changed, 21 insertions(+), 23 deletions(-) >> >> diff --git a/arch/arm64/include/asm/cpufeature.h b/arch/arm64/include/asm/cpufeature.h >> index ac67cfc2585a..0564e14616eb 100644 >> --- a/arch/arm64/include/asm/cpufeature.h >> +++ b/arch/arm64/include/asm/cpufeature.h >> @@ -304,6 +304,22 @@ static inline u64 read_zcr_features(void) >> return zcr; >> } >> >> +static inline u32 id_aa64mmfr0_parange_to_phys_shift(int parange) >> +{ >> + switch (parange) { >> + case 0: return 32; >> + case 1: return 36; >> + case 2: return 40; >> + case 3: return 42; >> + case 4: return 44; >> + >> + default: > > What is the case we want to cater for with making parange == 5 the > default for unrecognized values? > > (I have a feeling that default label comes from making the compiler > happy about potentially uninitialized values once upon a time before a > lot of refactoring happened here.) That is there to make sure we return 48 iff 52bit support (for that matter, if there is a new limit in the future) is not enabled. > >> + case 5: return 48; >> +#ifdef CONFIG_ARM64_PA_BITS_52 >> + case 6: return 52; >> +#endif >> + } >> +} >> #endif /* __ASSEMBLY__ */ >> >> > > Could you fold this change into the commit as well: > > diff --git a/arch/arm64/kvm/hyp/s2-setup.c b/arch/arm64/kvm/hyp/s2-setup.c > index 603e1ee83e89..eea2fbd68b8a 100644 > --- a/arch/arm64/kvm/hyp/s2-setup.c > +++ b/arch/arm64/kvm/hyp/s2-setup.c > @@ -29,7 +29,8 @@ u32 __hyp_text __init_stage2_translation(void) > /* > * Read the PARange bits from ID_AA64MMFR0_EL1 and set the PS > * bits in VTCR_EL2. Amusingly, the PARange is 4 bits, while > - * PS is only 3. Fortunately, bit 19 is RES0 in VTCR_EL2... > + * PS is only 3. Fortunately, only three bits is actually used to > + * enode the supported PARange values. > */ > parange = read_sysreg(id_aa64mmfr0_el1) & 7; > if (parange > ID_AA64MMFR0_PARANGE_MAX) Sure. Thanks for the review. Suzuki