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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3CCA2EB64D7 for ; Mon, 26 Jun 2023 16:35:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc: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=mioKe99pWFmX2d8FuPscKexyOIl4eCB/cjf15a0Pp0s=; b=NLJZCrBuUlAfwC cE2aMwsp8g/shv8neyXMJ7mD45mDppJp5QP7MCmqbcPCvbCvSnVx4WIewLORTLNjBtaQdZExHOUCP 9/8+5qT69zAy4ruRk2rbWQJ0BLpwDpXuiUtSFVidnyqyjeuP796vwo6MufoiJx7eG2xOPuRrp7JR4 kXz1UxkIyGDchKSHrX2Q0dG+VATM4IfdGydP/gN8e2q/3rqnYBQ1oLRJulz23kTkZvmrRkxFbQpEK 1ThzgJFm7sXONDuBvJ9j8t4J96475yQcPWBkxoLlvO6ZRihLUcn+Xx+7NpjIbJzFiElU1Blkcabz8 0GOBkttYJ1qvXRbV+rfg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qDpBH-00Af8F-3C; Mon, 26 Jun 2023 16:35:11 +0000 Received: from out-60.mta0.migadu.com ([2001:41d0:1004:224b::3c]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qDpBB-00Af7W-25 for linux-arm-kernel@lists.infradead.org; Mon, 26 Jun 2023 16:35:09 +0000 Date: Mon, 26 Jun 2023 16:34:50 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1687797296; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=BaphbRu7L4C7SqsGphPReeAVmMfd4ld7jXFvqYy0b30=; b=bVkV1Jem7YJ4Ng8rnGrW/tRpQl6E2EJLWyml/T7kGX7rpZ9A8Va8t42q9E25e+Wwl8yzh1 8auSyJlzC27hRiSOoRLO2oBsVQ5bnCyvbhzJlsXtNqm8U+ao53lTVPluAt3DIZTyLYZzqT C/natIyDXGMOS6gu5nFRZlyJcMYhAUo= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Oliver Upton To: Jing Zhang Cc: KVM , KVMARM , ARMLinux , Marc Zyngier , Oliver Upton , Will Deacon , Paolo Bonzini , James Morse , Alexandru Elisei , Suzuki K Poulose , Fuad Tabba , Reiji Watanabe , Raghavendra Rao Ananta , Suraj Jitindar Singh Subject: Re: [PATCH v4 1/4] KVM: arm64: Enable writable for ID_AA64DFR0_EL1 Message-ID: References: <20230607194554.87359-1-jingzhangos@google.com> <20230607194554.87359-2-jingzhangos@google.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20230607194554.87359-2-jingzhangos@google.com> X-Migadu-Flow: FLOW_OUT X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230626_093508_113601_5033794A X-CRM114-Status: GOOD ( 23.10 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 Wed, Jun 07, 2023 at 07:45:51PM +0000, Jing Zhang wrote: > Since number of context-aware breakpoints must be no more than number > of supported breakpoints according to Arm ARM, return an error if > userspace tries to set CTX_CMPS field to such value. > > Signed-off-by: Jing Zhang > --- > arch/arm64/kvm/sys_regs.c | 9 +++++++-- > 1 file changed, 7 insertions(+), 2 deletions(-) > > diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c > index 50d4e25f42d3..a6299c796d03 100644 > --- a/arch/arm64/kvm/sys_regs.c > +++ b/arch/arm64/kvm/sys_regs.c > @@ -1539,9 +1539,14 @@ static int set_id_aa64dfr0_el1(struct kvm_vcpu *vcpu, > const struct sys_reg_desc *rd, > u64 val) > { > - u8 pmuver, host_pmuver; > + u8 pmuver, host_pmuver, brps, ctx_cmps; > bool valid_pmu; > > + brps = FIELD_GET(ID_AA64DFR0_EL1_BRPs_MASK, val); > + ctx_cmps = FIELD_GET(ID_AA64DFR0_EL1_CTX_CMPs_MASK, val); > + if (ctx_cmps > brps) > + return -EINVAL; > + I'm not fully convinced on the need to do this sort of cross-field validation... I think it is probably more trouble than it is worth. If userspace writes something illogical to the register, oh well. All we should care about is that the advertised feature set is a subset of what's supported by the host. The series doesn't even do complete sanity checking, and instead works on a few cherry-picked examples. AA64PFR0.EL{0-3} would also require special handling depending on how pedantic you're feeling. AArch32 support at a higher exception level implies AArch32 support at all lower exception levels. But that isn't a suggestion to implement it, more of a suggestion to just avoid the problem as a whole. > host_pmuver = kvm_arm_pmu_get_pmuver_limit(); > > /* > @@ -2061,7 +2066,7 @@ static const struct sys_reg_desc sys_reg_descs[] = { > .get_user = get_id_reg, > .set_user = set_id_aa64dfr0_el1, > .reset = read_sanitised_id_aa64dfr0_el1, > - .val = ID_AA64DFR0_EL1_PMUVer_MASK, }, > + .val = GENMASK(63, 0), }, DebugVer requires special handling, as the minimum safe value is 0x6 for the field. IIUC, as written we would permit userspace to write any value less than the current register value. I posted a patch to 'fix' this, but it isn't actually a bug in what's upstream. Could you pick that patch up and discard the 'Fixes' tag on it? https://lore.kernel.org/kvmarm/20230623205232.2837077-1-oliver.upton@linux.dev/ > ID_SANITISED(ID_AA64DFR1_EL1), > ID_UNALLOCATED(5,2), > ID_UNALLOCATED(5,3), > -- > 2.41.0.rc0.172.g3f132b7071-goog > > -- Thanks, Oliver _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel