Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp4238251pxj; Tue, 25 May 2021 03:32:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxOC+20gKOuicaakg0gP/i4PpJ5kFdlsqZ0Q2uFW6S0uKOcm6Qn2Kn3CEwGFsRa+2P9/U/i X-Received: by 2002:a17:906:a245:: with SMTP id bi5mr29124968ejb.316.1621938747031; Tue, 25 May 2021 03:32:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621938747; cv=none; d=google.com; s=arc-20160816; b=Bsp0QiMcgZVaVuOYJ+gAn8rrD+g3tHA9JNefgmqhXRsqVT+s9ogma8Sy+HNgiLcCXj aZybNqeye0dRPk5ULUDrFB/an2zfNmRjpIMcehKIg6QuCtL08WQiYRSloW2N55TFyNmT P/tC1nTVhizwY7egiqxUKoE3laj9KtXogoEweugrVrxrLaa6MYDStHNxHjbO6XY2sfP7 Pnj7zWTc2iVeIc3Iuab0lU38nq+jXAsyfbDuyiquvODE4EZYToQrUmP5zImaGreRKb6k l7LI5XXXEYAU7wTdBI19BMC1jvlcPylawT8l0RQsNtR3v+PptgXWEfMhrDl9eGfrTul4 q/3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=iZdsDdicmfoo2Aiv8TUYAimfm+a7yn7XvNr14JKfdjw=; b=xTj21pEHqRrFqLXIPr0JKwRXExPSPD5SdpDXCGPZoaRXgqkXonc3VQUNxnzzaKcRYB D7ABmb5q0kBINQHYo3x8xccWX8j5U45OpTuhN8TWFmNS9Dkc83zi+FFbS+ctwc/xTl8g U17c1hqcC4K5bT6lu36d7bp8prvCOXx2qsUk48ZlqDJfzWx2m7Zc45p7O2anIiXxiR/y nTPtT26P6MIYIAHZIPFdAj1/bICkIX4ZvWXo1DSUjHSAhqUf4lo3wXiGVe3HI17SAx6K zR9Yewcze6jlwGKKuu69qUAQg6HfWz8TSNSjwEffyytQQHcWVtyE6wOBoytN701++1do fEZA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l17si14657331eja.456.2021.05.25.03.32.03; Tue, 25 May 2021 03:32:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232663AbhEYJpV (ORCPT + 99 others); Tue, 25 May 2021 05:45:21 -0400 Received: from mail.kernel.org ([198.145.29.99]:42472 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230508AbhEYJpV (ORCPT ); Tue, 25 May 2021 05:45:21 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 0E39B61409; Tue, 25 May 2021 09:43:48 +0000 (UTC) Date: Tue, 25 May 2021 10:43:46 +0100 From: Catalin Marinas To: Will Deacon Cc: linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, Marc Zyngier , Greg Kroah-Hartman , Peter Zijlstra , Morten Rasmussen , Qais Yousef , Suren Baghdasaryan , Quentin Perret , Tejun Heo , Li Zefan , Johannes Weiner , Ingo Molnar , Juri Lelli , Vincent Guittot , "Rafael J. Wysocki" , kernel-team@android.com Subject: Re: [PATCH v6 18/21] arm64: Prevent offlining first CPU with 32-bit EL0 on mismatched system Message-ID: <20210525094346.GB15564@arm.com> References: <20210518094725.7701-1-will@kernel.org> <20210518094725.7701-19-will@kernel.org> <20210524154657.GE14645@arm.com> <20210524203249.GD15545@willie-the-truck> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210524203249.GD15545@willie-the-truck> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 24, 2021 at 09:32:50PM +0100, Will Deacon wrote: > On Mon, May 24, 2021 at 04:46:58PM +0100, Catalin Marinas wrote: > > On Tue, May 18, 2021 at 10:47:22AM +0100, Will Deacon wrote: > > > diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c > > > index 959442f76ed7..72efdc611b14 100644 > > > --- a/arch/arm64/kernel/cpufeature.c > > > +++ b/arch/arm64/kernel/cpufeature.c > > > @@ -2896,15 +2896,33 @@ void __init setup_cpu_features(void) > > > > > > static int enable_mismatched_32bit_el0(unsigned int cpu) > > > { > > > + static int lucky_winner = -1; > > > + > > > struct cpuinfo_arm64 *info = &per_cpu(cpu_data, cpu); > > > bool cpu_32bit = id_aa64pfr0_32bit_el0(info->reg_id_aa64pfr0); > > > > > > if (cpu_32bit) { > > > cpumask_set_cpu(cpu, cpu_32bit_el0_mask); > > > static_branch_enable_cpuslocked(&arm64_mismatched_32bit_el0); > > > - setup_elf_hwcaps(compat_elf_hwcaps); > > > } > > > > > > + if (cpumask_test_cpu(0, cpu_32bit_el0_mask) == cpu_32bit) > > > + return 0; > > > > I don't fully understand this early return. AFAICT, we still call > > setup_elf_hwcaps() via setup_cpu_features() if the system supports > > 32-bit EL0 (mismatched or not) at boot. For CPU hotplug, we can add the > > compat hwcaps later if we didn't set them up at boot. So this part is > > fine. > > > > However, if CPU0 is 32-bit-capable, it looks like we'd never disable the > > offlining on any of the 32-bit-capable CPUs and there's nothing that > > prevents offlining CPU0. > > That is also deferred until we actually detect the mismatch. For example, if > CPU0 is 32-bit capable but none of the others are, then when we online CPU1 > we will print: > > | CPU features: Asymmetric 32-bit EL0 support detected on CPU 1; CPU hot-unplug disabled on CPU 0 > > so the check above is really asking "Is the CPU being onlined mismatched wrt > the boot CPU?". If yes, then we need to make sure that we're keeping a > 32-bit-capable CPU around. Got it now, the offlining will only be disabled if we detected a mismatch. For this patch: Reviewed-by: Catalin Marinas