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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 66E74C3DA4D for ; Thu, 17 Aug 2023 15:53:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1353361AbjHQPx0 (ORCPT ); Thu, 17 Aug 2023 11:53:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52374 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1353370AbjHQPxR (ORCPT ); Thu, 17 Aug 2023 11:53:17 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 580B230D8 for ; Thu, 17 Aug 2023 08:53:16 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 66CC0618C8 for ; Thu, 17 Aug 2023 15:53:10 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C6A9BC433C8; Thu, 17 Aug 2023 15:53:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1692287589; bh=ePXnfxRXUddVzI3u0tJHF8AuA23aR9K0higvYkyBCvQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=UQtZQAlJ4JGiz4IhxhQb5YLJwnWQHCzW0Rl159gwLZNzqAGw7OCbZg0ZaEjdbr5mE leUuNax9c9s55u1mkv91DXirYSyuZbq4w8ezDYYThf8LEH4gc/oIeYFTLCVaoDLgSG stkVYgf3PiQnKUvJgm6FsEvomy0GZxHD+DpCyLCLizE0AzLL6VGt+xhSwLTvJkqzIS egP7xl9qEaueEzT7Q1jSleh97QSbJgrHNtRZMWhV29aN+Dm55ciQtbGgZB9L1t9OuR 6eiZiIZ8MubHbZrBbfyBhpuxoX858pFVLtxRifxoN0GakjGykGta+xYRUZiV05AXGJ mCZWB0Jhn6UFA== Received: from sofa.misterjones.org ([185.219.108.64] helo=goblin-girl.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1qWfJ5-005j6p-FM; Thu, 17 Aug 2023 16:53:07 +0100 Date: Thu, 17 Aug 2023 16:53:07 +0100 Message-ID: <86pm3lfyxo.wl-maz@kernel.org> From: Marc Zyngier To: Jing Zhang Cc: KVM , KVMARM , ARMLinux , Oliver Upton , Will Deacon , Paolo Bonzini , James Morse , Alexandru Elisei , Suzuki K Poulose , Fuad Tabba , Reiji Watanabe , Raghavendra Rao Ananta , Suraj Jitindar Singh , Cornelia Huck Subject: Re: [PATCH v8 07/11] KVM: arm64: Enable writable for ID_AA64PFR0_EL1 In-Reply-To: <20230807162210.2528230-8-jingzhangos@google.com> References: <20230807162210.2528230-1-jingzhangos@google.com> <20230807162210.2528230-8-jingzhangos@google.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/28.2 (aarch64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: jingzhangos@google.com, kvm@vger.kernel.org, kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org, oliver.upton@linux.dev, will@kernel.org, pbonzini@redhat.com, james.morse@arm.com, alexandru.elisei@arm.com, suzuki.poulose@arm.com, tabba@google.com, reijiw@google.com, rananta@google.com, surajjs@amazon.com, cohuck@redhat.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Mon, 07 Aug 2023 17:22:05 +0100, Jing Zhang wrote: > > All valid fields in ID_AA64PFR0_EL1 are writable from usrespace > with this change. userspace > > Signed-off-by: Jing Zhang > --- > arch/arm64/kvm/sys_regs.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c > index 879004fd37e5..392613bec560 100644 > --- a/arch/arm64/kvm/sys_regs.c > +++ b/arch/arm64/kvm/sys_regs.c > @@ -2041,7 +2041,7 @@ static const struct sys_reg_desc sys_reg_descs[] = { > .get_user = get_id_reg, > .set_user = set_id_reg, > .reset = read_sanitised_id_aa64pfr0_el1, > - .val = ID_AA64PFR0_EL1_CSV2_MASK | ID_AA64PFR0_EL1_CSV3_MASK, }, > + .val = GENMASK(63, 0), }, > ID_SANITISED(ID_AA64PFR1_EL1), > ID_UNALLOCATED(4,2), > ID_UNALLOCATED(4,3), Same remark as the previous patch. What makes it legal to make *everything* writable? For example, we don't expose the AMU. And yet you are telling userspace "sure, go ahead". Userspace will then try and restore *something*, and will eventually crap itself because the kernel won't allow it. Why do we bother describing the writable fields if userspace can't write to them? M. -- Without deviation from the norm, progress is not possible.