Received: by 10.223.176.46 with SMTP id f43csp2824147wra; Mon, 22 Jan 2018 04:07:18 -0800 (PST) X-Google-Smtp-Source: AH8x226v0SUklhzRDuLVMnDgcgb0QSNxGvqnqGZgeX3PDaLiF3oQ0Om2+t699Rr2Zh5RUntgnjOR X-Received: by 2002:a17:902:7003:: with SMTP id y3-v6mr3442307plk.449.1516622837993; Mon, 22 Jan 2018 04:07:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516622837; cv=none; d=google.com; s=arc-20160816; b=yViLj8wEmkfKo1DSVWRn/4M85dPMEybmKNOZB1bseMHD3PvdTEj4erQErPK9Moi4lz Rz1geY0uC1SC7wuEYj0Mq2Bdnt6yBXWYfT8c5lS41o38CaKtPY0NqmtqxRgm9CzfVLtz qopbhaWWroEe5Tt6HNYRSgbumza6SQNTya1hrwTsNEawbwbhY/4f16ElTFC6ksz2KHp1 VUC5tgtl+gTyeBRSHyUy46DD3gZFkhzA+/MPg/i0knMRrA1AcNx2sUP96RPVSeYpI3VY u+cDOCiB4YqRKCCQsU2PLKiCg9U6Hne9ONrKPyrvm1h0MqAQlaWmzjRZ6zlbBV6TfjSQ /q1w== 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=zkkWLgk5PLD+WYcRRmm5XzouBXHyENg0L7IcUJfu9lI=; b=HNbA+jR9ypXQC+5C0WQj2aputNGxejbvfn9y5klI2vmewZac4mR/YHbcm/GQvO2Bkz P2YDxzuHEHr5wq7L1eJz8kXqluvyuaxzpTUKeWQCr2BOJoI389Uhu9JuUu5B1Ty77JHT hxEnu/SYG484L0uQtiAd1O46WhxE9E+I9+2TnCLocsWzXBjwh6blhVNZBhsJTnju24uy +lOcd5ek/2NrZiIg6utQ0AIjNDuVx1sB/kJkKqzkXueWvC/gonidHeOxegGsWimDOOfW Aq5NjWkh5GOJHkfUqPGA9v1fig0gKKXU9F5trRdBUupvlDIqI85xunIVHeh6WN0TykQ5 dvyA== 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 w8si1718459pgt.575.2018.01.22.04.07.04; Mon, 22 Jan 2018 04:07:17 -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 S1751149AbeAVMGF (ORCPT + 99 others); Mon, 22 Jan 2018 07:06:05 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:57944 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751024AbeAVMGE (ORCPT ); Mon, 22 Jan 2018 07:06:04 -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 D3C1B1529; Mon, 22 Jan 2018 04:06:03 -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 8B0273F53D; Mon, 22 Jan 2018 04:05:55 -0800 (PST) Subject: Re: [PATCH v2 1/6] arm64: cpufeature: Allow early detect of specific features To: Julien Thierry , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Cc: mark.rutland@arm.com, marc.zyngier@arm.com, james.morse@arm.com, daniel.thompson@linaro.org, Catalin Marinas , Will Deacon References: <1516190084-18978-1-git-send-email-julien.thierry@arm.com> <1516190084-18978-2-git-send-email-julien.thierry@arm.com> From: Suzuki K Poulose Message-ID: Date: Mon, 22 Jan 2018 12:05:52 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <1516190084-18978-2-git-send-email-julien.thierry@arm.com> 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 17/01/18 11:54, Julien Thierry wrote: > From: Daniel Thompson > > Currently it is not possible to detect features of the boot CPU > until the other CPUs have been brought up. > > This prevents us from reacting to features of the boot CPU until > fairly late in the boot process. To solve this we allow a subset > of features (that are likely to be common to all clusters) to be > detected based on the boot CPU alone. > > Signed-off-by: Daniel Thompson > [julien.thierry@arm.com: check non-boot cpu missing early features, avoid > duplicates between early features and normal > features] > Signed-off-by: Julien Thierry > Cc: Catalin Marinas > Cc: Will Deacon > Cc: Suzuki K Poulose > --- > arch/arm64/kernel/cpufeature.c | 69 ++++++++++++++++++++++++++++-------------- > 1 file changed, 47 insertions(+), 22 deletions(-) > > diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c > index a73a592..6698404 100644 > --- a/arch/arm64/kernel/cpufeature.c > +++ b/arch/arm64/kernel/cpufeature.c > @@ -52,6 +52,8 @@ > DECLARE_BITMAP(cpu_hwcaps, ARM64_NCAPS); > EXPORT_SYMBOL(cpu_hwcaps); > > +static void __init setup_early_feature_capabilities(void); > + > /* > * Flag to indicate if we have computed the system wide > * capabilities based on the boot time active CPUs. This > @@ -542,6 +544,8 @@ void __init init_cpu_features(struct cpuinfo_arm64 *info) > init_cpu_ftr_reg(SYS_ZCR_EL1, info->reg_zcr); > sve_init_vq_map(); > } > + > + setup_early_feature_capabilities(); > } > > static void update_cpu_ftr_reg(struct arm64_ftr_reg *reg, u64 new) > @@ -846,7 +850,7 @@ static bool has_no_fpsimd(const struct arm64_cpu_capabilities *entry, int __unus > ID_AA64PFR0_FP_SHIFT) < 0; > } > > -static const struct arm64_cpu_capabilities arm64_features[] = { > +static const struct arm64_cpu_capabilities arm64_early_features[] = { > { > .desc = "GIC system register CPU interface", > .capability = ARM64_HAS_SYSREG_GIC_CPUIF, > @@ -857,6 +861,10 @@ static bool has_no_fpsimd(const struct arm64_cpu_capabilities *entry, int __unus > .sign = FTR_UNSIGNED, > .min_field_value = 1, > }, > + {} > +}; > + Julien, One potential problem with this is that we don't have a way to make this work on a "theoretical" system with and without GIC system reg interface. i.e, if we don't have the CONFIG enabled for using ICC system regs for IRQ flags, the kernel could still panic. I understand this is not a "normal" configuration but, may be we could make the panic option based on whether we actually use the system regs early enough ? Btw, I am rewriting the capabilities infrastructure to allow per-cap control on how it should be treated. I might add an EARLY scope for caps which could cover this and may be VHE. Suzuki