From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0E5C6C433E7 for ; Fri, 9 Oct 2020 08:41:40 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 7F4632087D for ; Fri, 9 Oct 2020 08:41:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="SiNQWM7v"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="DMeSUc9J" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7F4632087D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=E8A+g/WZbvvkgrIcbg4hq40GgWyFoXqIOZ4dEac0RbQ=; b=SiNQWM7v/lt2RVHGo29kR5GpN wLTlKDsS/zmFo6CImW8RNolN/yACc9sc9ot3QL1M7t4i2qFw+fbEwG27MV4oQWCCfRRWPCdgp6XHi olI2yDoqnhyEGz8Bp/uudsjCmqzmyi+Xql79MyZ2256rhxvlLwGdUTYzayS9PL1oisZje58A3k3Z6 FUgl1zF4Rmj0y6aRfO/aliCAACxmJkn4tE3MJW4XEITquaKtXT4RISJN/q/G1uUTvGE+g4t9bLLnK 0qMBv+I1f6GvekwIXOreHMqrNzMUPNkWe//CT13KohyJxMJGJl4GlQEdh/YYfAFxpVaG9/VeQOaZn G7cgHygPw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kQnwm-0005KF-Lv; Fri, 09 Oct 2020 08:40:16 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kQnwj-0005J5-Rp for linux-arm-kernel@lists.infradead.org; Fri, 09 Oct 2020 08:40:15 +0000 Received: from willie-the-truck (236.31.169.217.in-addr.arpa [217.169.31.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3C3A12087D; Fri, 9 Oct 2020 08:40:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1602232812; bh=3FnNRrdFZy8dpkVRh9duQr65KKRLcp5XuZqmODbiGFI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=DMeSUc9JZDrvNMltlX3QyR/dLxuPDyT2wQ+MEhojEqCyMgsTc5n3+Gi3/7Eh3bQis XZtZdASUjMV37MkDMtvIXGfeAnmy1MeFniAk617NWFq4v/O0+lbL2KBSdBliNIT5yQ jcyk1TQItgRC5flgX9F2GhlE2kG2sMHvb2/ropu4= Date: Fri, 9 Oct 2020 09:40:07 +0100 From: Will Deacon To: Greg Kroah-Hartman Subject: Re: [RFC PATCH 2/3] arm64: Add support for asymmetric AArch32 EL0 configurations Message-ID: <20201009084007.GB29594@willie-the-truck> References: <20201008181641.32767-1-qais.yousef@arm.com> <20201008181641.32767-3-qais.yousef@arm.com> <20201009061356.GA120580@kroah.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20201009061356.GA120580@kroah.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201009_044014_272362_682985FA X-CRM114-Status: GOOD ( 29.07 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-arch@vger.kernel.org, "Peter Zijlstra \(Intel\)" , Catalin Marinas , Morten Rasmussen , Marc Zyngier , Linus Torvalds , Qais Yousef , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Oct 09, 2020 at 08:13:56AM +0200, Greg Kroah-Hartman wrote: > On Thu, Oct 08, 2020 at 07:16:40PM +0100, Qais Yousef wrote: > > When the CONFIG_ASYMMETRIC_AARCH32 option is enabled (EXPERT), the type > > of the ARM64_HAS_32BIT_EL0 capability becomes WEAK_LOCAL_CPU_FEATURE. > > The kernel will now return true for system_supports_32bit_el0() and > > checks 32-bit tasks are affined to AArch32 capable CPUs only in > > do_notify_resume(). If the affinity contains a non-capable AArch32 CPU, > > the tasks will get SIGKILLed. If the last CPU supporting 32-bit is > > offlined, the kernel will SIGKILL any scheduled 32-bit tasks (the > > alternative is to prevent offlining through a new .cpu_disable feature > > entry). > > > > In addition to the relaxation of the ARM64_HAS_32BIT_EL0 capability, > > this patch factors out the 32-bit cpuinfo and features setting into > > separate functions: __cpuinfo_store_cpu_32bit(), > > init_cpu_32bit_features(). The cpuinfo of the booting CPU > > (boot_cpu_data) is now updated on the first 32-bit capable CPU even if > > it is a secondary one. The ID_AA64PFR0_EL0_64BIT_ONLY feature is relaxed > > to FTR_NONSTRICT and FTR_HIGHER_SAFE when the asymmetric AArch32 support > > is enabled. The compat_elf_hwcaps are only verified for the > > AArch32-capable CPUs to still allow hotplugging AArch64-only CPUs. > > > > Make sure that KVM never sees the asymmetric 32bit system. Guest can > > still ignore ID registers and force run 32bit at EL0. > > > > Co-developed-by: Qais Yousef > > Signed-off-by: Catalin Marinas > > Signed-off-by: Qais Yousef > > --- > > arch/arm64/Kconfig | 14 ++++++ > > arch/arm64/include/asm/cpu.h | 2 + > > arch/arm64/include/asm/cpucaps.h | 3 +- > > arch/arm64/include/asm/cpufeature.h | 20 +++++++- > > arch/arm64/include/asm/thread_info.h | 5 +- > > arch/arm64/kernel/cpufeature.c | 66 +++++++++++++++----------- > > arch/arm64/kernel/cpuinfo.c | 71 ++++++++++++++++++---------- > > arch/arm64/kernel/process.c | 17 +++++++ > > arch/arm64/kernel/signal.c | 18 +++++++ > > arch/arm64/kvm/arm.c | 5 +- > > arch/arm64/kvm/guest.c | 2 +- > > arch/arm64/kvm/sys_regs.c | 14 +++++- > > 12 files changed, 176 insertions(+), 61 deletions(-) > > > > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig > > index 6d232837cbee..591853504dc4 100644 > > --- a/arch/arm64/Kconfig > > +++ b/arch/arm64/Kconfig > > @@ -1868,6 +1868,20 @@ config DMI > > > > endmenu > > > > +config ASYMMETRIC_AARCH32 > > + bool "Allow support for asymmetric AArch32 support" > > + depends on COMPAT && EXPERT > > Why EXPERT? You don't want this able to be enabled by anyone? TBH, I'd be inclined to drop the Kconfig option altogether. We're not looking at a lot of code here, so all it does is further fragment the build testing we get from CI (or it just ends up being enabled all of the time). A cmdline option, on the other hand, makes a tonne of sense to me, as it acts as an "opt-in" that the distribution is ready to handle the madness (because userspace will need to care about this even with the scheduler hacks proposed here). Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel