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 26D9DEB64DC for ; Wed, 21 Jun 2023 07:30:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229796AbjFUHaK (ORCPT ); Wed, 21 Jun 2023 03:30:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58362 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229849AbjFUHaI (ORCPT ); Wed, 21 Jun 2023 03:30:08 -0400 Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3755810FF for ; Wed, 21 Jun 2023 00:30:06 -0700 (PDT) Received: by mail-ej1-x62b.google.com with SMTP id a640c23a62f3a-987341238aeso676231866b.3 for ; Wed, 21 Jun 2023 00:30:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ventanamicro.com; s=google; t=1687332604; x=1689924604; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=ZmyDfnK9tJh8eswYvjmWTei7tQJVIfXBxXoVL4SG7R8=; b=AErp9BkT1HOnQXLDaZG2ZhhgiFqoujRXuDRZ6mNMc66uo4iADPH8ND6vVT11LgrTTL AylPEuDYLAbzHcWd6s9RIjOsgstMtxC5b9BLtSsAOyK2HGqgHC3fff3Y4oZ7Y6VrxRlb xSE2jauM8NDE34EUg1l7tNFFj85RKWqV6X4jlUmegTW9fKm1MGIzqBLlvT7Dk2psnP4Y 8HbScXfthtVm8E5V+taPq0gF55iLE02AnUSQSRYRIhOz37xoTjciAU4olKLgmAwzKjUw VAxO82NHkTCDWNCuSI/RyrXR9+cfwhF5scfDxoKd+zT2dCML+89Tp+fKPi19rwUbwudh B7nA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687332604; x=1689924604; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ZmyDfnK9tJh8eswYvjmWTei7tQJVIfXBxXoVL4SG7R8=; b=hJzJyVk9crWpWpPwMZD6x5so+KsGp2OFsqMLTp328p+RA23QCD4ATsfSxukn3BKr7L XR7W4ffj/XmMPQkPWrTXs/ypIf+rEWLVa91CdKSuxIJ/8OlEJKv5m8mp1wm6gzRLArN3 YJ8mgFeedMcwQOZwXDvZG3Q81svHRsSb5uednxCQ0ZiuW3s/a2E2HP5pCfkzJakHHiA+ KD2Knz2Z4glY/49Uagq9Y9vLkcxwGc5lzgHfCEjLfbrogDGVBoYDdc2mI7pVGjRF1//E uxd9SKSs9MEr1LuHVeMr+A+vpFNc7Xh6WQ2LQm+ymVby4BMQyWDdUUsyCdeZfVA4px8k g3bA== X-Gm-Message-State: AC+VfDxkUJIApIVUJCKQjLBlfg0vgmRzifSV7mrUgGLTf19BONCtq0Ec G5ncmEvJoQ6BYu9PL03O0S/3sg== X-Google-Smtp-Source: ACHHUZ71iRvfbRckg3Spoocjgf5Ljr6HcH7QnRCM6WqfLPyHhFnJWAR3zMooBAb60KO2iMTWfdWlMw== X-Received: by 2002:a17:906:9b88:b0:988:8fed:8ae9 with SMTP id dd8-20020a1709069b8800b009888fed8ae9mr7743704ejc.37.1687332604526; Wed, 21 Jun 2023 00:30:04 -0700 (PDT) Received: from localhost (2001-1ae9-1c2-4c00-20f-c6b4-1e57-7965.ip6.tmcz.cz. [2001:1ae9:1c2:4c00:20f:c6b4:1e57:7965]) by smtp.gmail.com with ESMTPSA id n17-20020a17090625d100b00988c6ac6b86sm2631710ejb.186.2023.06.21.00.30.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Jun 2023 00:30:03 -0700 (PDT) Date: Wed, 21 Jun 2023 09:30:02 +0200 From: Andrew Jones To: Haibo Xu Cc: Haibo Xu , maz@kernel.org, oliver.upton@linux.dev, seanjc@google.com, Paolo Bonzini , Jonathan Corbet , Anup Patel , Atish Patra , Paul Walmsley , Palmer Dabbelt , Albert Ou , Shuah Khan , James Morse , Suzuki K Poulose , Zenghui Yu , Ben Gardon , David Matlack , Vipin Sharma , Colton Lewis , kvm@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kselftest@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev Subject: Re: [PATCH v3 10/10] KVM: riscv: selftests: Add get-reg-list test Message-ID: <20230621-37ea9461250036cc2ec8c544@orel> References: <8cd4ce50f5f4a639f4508085959aae222d4d4386.1686275310.git.haibo1.xu@intel.com> <20230609-fba04b424a4d46574e04e587@orel> <20230620-95ce8ab70956a72b9da3a31a@orel> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Wed, Jun 21, 2023 at 09:55:13AM +0800, Haibo Xu wrote: > On Tue, Jun 20, 2023 at 6:44 PM Andrew Jones wrote: > > > > On Tue, Jun 20, 2023 at 06:05:59PM +0800, Haibo Xu wrote: > > > On Fri, Jun 9, 2023 at 9:35 PM Andrew Jones wrote: > > > > > > > > On Fri, Jun 09, 2023 at 10:12:18AM +0800, Haibo Xu wrote: > > > > > +static struct vcpu_reg_list aia_config = { > > > > > + .sublists = { > > > > > + BASE_SUBLIST, > > > > > + AIA_REGS_SUBLIST, > > > > > + {0}, > > > > > + }, > > > > > +}; > > > > > + > > > > > +static struct vcpu_reg_list fp_f_d_config = { > > > > > + .sublists = { > > > > > + BASE_SUBLIST, > > > > > + FP_F_REGS_SUBLIST, > > > > > + FP_D_REGS_SUBLIST, > > > > > + {0}, > > > > > + }, > > > > > +}; > > > > > + > > > > > +struct vcpu_reg_list *vcpu_configs[] = { > > > > > + &zicbo_config, > > > > > + &aia_config, > > > > > + &fp_f_d_config, > > > > > +}; > > > > > +int vcpu_configs_n = ARRAY_SIZE(vcpu_configs); > > > > > -- > > > > > 2.34.1 > > > > > > > > > > > > > I see we have a bit of a problem with the configs for riscv. Since we > > > > don't disable anything we're not testing, then for any test that is > > > > missing, for example, the f and d registers, we'll get output like > > > > "There are 66 new registers. Consider adding them to the blessed reg > > > > list with the following lines:" and then a dump of all the f and d > > > > registers. The test doesn't fail, but it's messy and confusing. Ideally > > > > we'd disable all registers of all sublists not in the config, probably > > > > by starting by disabling everything and then only reenabling the ones > > > > in the config. > > > > > > > > Anything that can't be disabled is either a KVM bug, i.e. we should > > > > be able to disable it, because we can't expect every host to have it, > > > > or it needs to be in the base register sublist (meaning every host > > > > will always have it). > > > > > > > > > > HI Andrew, > > > > > > I found several multi-letters ISA EXT(AIA/SSTC etc) were not allowed > > > to be disabled. > > > Is it a bug? shall we fix it？ > > > > Extensions that a guest could use (regardless of whether or not the host > > described it in the guest's isa string), because the instructions or CSR > > accesses don't trap, can't truly be disabled. So, it's not a bug to > > prohibit disabling them and indeed the test cases should actually ensure > > disabling them fails. > > > > So these kinds of ISA_EXT_* regs should be in the base reg list, right? > Ah, this is getting a bit messy. We don't want all these extensions in a "base", which represents extensions for all possible hosts, because the extensions are optional, but, we can't remove them from get-reg-list output by disabling them, since they can't be disabled. It seems we need the concept of "base", which is the common set expected on all hosts, and also the concept of "this host's base". I'm struggling to think of a nice way to deal with that. A first thought is to both add these types of registers to their own extension-specific sublists and to filter_reg(). I think that will keep them from being reported as new registers in every test, but also allow detection of them going missing when they're extension is present. Thanks, drew