Message ID | 20221024113445.1022147-19-wei.w.wang@intel.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:6687:0:0:0:0:0 with SMTP id l7csp394866wru; Mon, 24 Oct 2022 04:41:12 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5IYz5EYCLaAPtDJ58lIcFcsm4+HvvpgiWLw78wwH4RvKz8MbAg1LZ1w5otT2hxVvGW9WfL X-Received: by 2002:a17:906:8a47:b0:7a5:8160:19a6 with SMTP id gx7-20020a1709068a4700b007a5816019a6mr6092934ejc.477.1666611671932; Mon, 24 Oct 2022 04:41:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666611671; cv=none; d=google.com; s=arc-20160816; b=yA2HqcT3JoObDFPi5OrFhTmu5UgV/fSIGeyLyxdop08CRjIDUVb2Tt9u4GdjX1iiQd yzZQ0B+UCepS6JdzxSrnNsSrbunhlabDc8y02x/1zQhP0dYF+gwVYr25+227NJpJVXYp H9s7LPzajb14wIV9YIeUIQ+/PDfnJuXVVDRaF/nVrZJGzJYXDnQ7SeZQffXI5zp+uTYH 5+8hIUK2HnbGcdRM+jWnqEgJVgAnJPbE2TOueHgNQ8PKCBUjlL1KqaY78wwBCVBs4OVc O1mDc7yHAkBXraTsSDbXaSLEI4iW2habMPechCt3iDcsl8zgjAYFpAi+Q//gesR+hpJ+ 13cQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=RFF0ZkMzxjnk+P7udhWyIbAR55rPVMyNUTVhr9cQdpE=; b=er2xLofxyPfpXJt+ek8DW9B4KDkzMnY03uuLfiWlagazgG2sqk0u9btSy5BYfo9/lg KFz7NsPJKHyuVvO08l/wHtq/gVc22OK9N6XQGt4cicPHtrd4PAcJ+KeGw4QTDp+lnScy QkHK7RAmbsKzhgediDRYlOTnOQ3YMTJt61YfPsLvUXLYvTgsBjkltuarf0EgUBAFa/MF ATw5h+cVGqUVLcnBmVSRTcVTV9HhvtBn/WnOXa4bKjVxC6GUGs4CHGZvfpdVG7SnFyig T4eYv6JRHuCBVbVtKNy6Vowaq+z5bYjSVhIBzosC0QmtLqFVVvJ162aCMrlNv1vERPMe AMTw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=FWgR9JmZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id r15-20020a17090638cf00b0078e11e92257si23315125ejd.333.2022.10.24.04.40.47; Mon, 24 Oct 2022 04:41:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=FWgR9JmZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231338AbiJXLkI (ORCPT <rfc822;pwkd43@gmail.com> + 99 others); Mon, 24 Oct 2022 07:40:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37990 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231289AbiJXLi7 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 24 Oct 2022 07:38:59 -0400 Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 65C496D877; Mon, 24 Oct 2022 04:38:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1666611494; x=1698147494; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=V5CMqFlWnS5AeCB0CE61Ephj3ol/+ZP60Gy/5sHQJ6E=; b=FWgR9JmZdq3Jga8/AXjnwgFwNWgipP9yWdJnBRqqDmLizCdgaMOWNGIJ fuKbFlT77/El+F83NAwRR5JvcfY0LMjyFUFIv1yPTioU4eYCa+tTyxENk KphQaczZSDbkN4ElsXn5DTzmpggUob7YDB7+Ds8ux6PTrTGHhp8QkHnHh y1NY56PdiCdTkM/WBTfUKCBQ365G72ffgs+Bk6YWd5JH8o+qOnaEssY0p WRn/Blmw2Jqkk5rvZpRoV8CLbwdXdP5dY990fSSsONh+jdz9OfD7wvBv+ Mv4+E5/sU3vL5bMChBAiRxwN67a6gR3B5sq0LotOLSmp+AiRtxfsXDCvp A==; X-IronPort-AV: E=McAfee;i="6500,9779,10509"; a="369462511" X-IronPort-AV: E=Sophos;i="5.95,209,1661842800"; d="scan'208";a="369462511" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Oct 2022 04:35:34 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10509"; a="773785085" X-IronPort-AV: E=Sophos;i="5.95,209,1661842800"; d="scan'208";a="773785085" Received: from tdx-lm.sh.intel.com ([10.239.53.27]) by fmsmga001.fm.intel.com with ESMTP; 24 Oct 2022 04:35:32 -0700 From: Wei Wang <wei.w.wang@intel.com> To: seanjc@google.com, pbonzini@redhat.com Cc: dmatlack@google.com, vipinsh@google.com, ajones@ventanamicro.com, eric.auger@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Wei Wang <wei.w.wang@intel.com> Subject: [PATCH v1 18/18] KVM: selftests/kvm_create_max_vcpus: check KVM_MAX_VCPUS Date: Mon, 24 Oct 2022 19:34:45 +0800 Message-Id: <20221024113445.1022147-19-wei.w.wang@intel.com> X-Mailer: git-send-email 2.27.0 In-Reply-To: <20221024113445.1022147-1-wei.w.wang@intel.com> References: <20221024113445.1022147-1-wei.w.wang@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1747569000496205106?= X-GMAIL-MSGID: =?utf-8?q?1747569000496205106?= |
Series |
KVM selftests code consolidation and cleanup
|
|
Commit Message
Wang, Wei W
Oct. 24, 2022, 11:34 a.m. UTC
If the KVM side max vcpu number is larger than the one supported by the
userspace selftests, adjust the max number.
Signed-off-by: Wei Wang <wei.w.wang@intel.com>
---
tools/testing/selftests/kvm/kvm_create_max_vcpus.c | 7 +++++++
1 file changed, 7 insertions(+)
Comments
On Mon, Oct 24, 2022, Wei Wang wrote: > If the KVM side max vcpu number is larger than the one supported by the > userspace selftests, adjust the max number. No, this defeats the purpose of the test. "create max vCPUs" means "create the maximum number allowed by KVM", not "create the arbitrary max supported by selftests".
diff --git a/tools/testing/selftests/kvm/kvm_create_max_vcpus.c b/tools/testing/selftests/kvm/kvm_create_max_vcpus.c index 31b3cb24b9a7..bbdb371e21ed 100644 --- a/tools/testing/selftests/kvm/kvm_create_max_vcpus.c +++ b/tools/testing/selftests/kvm/kvm_create_max_vcpus.c @@ -50,6 +50,13 @@ int main(int argc, char *argv[]) pr_info("KVM_CAP_MAX_VCPU_ID: %d\n", kvm_max_vcpu_id); pr_info("KVM_CAP_MAX_VCPUS: %d\n", kvm_max_vcpus); + pr_info("selftests KVM_MAX_VCPUS: %d\n", KVM_MAX_VCPUS); + + if (kvm_max_vcpu_id > KVM_MAX_VCPUS) + kvm_max_vcpu_id = KVM_MAX_VCPUS; + + if (kvm_max_vcpus > KVM_MAX_VCPUS) + kvm_max_vcpus = KVM_MAX_VCPUS; /* * Check that we're allowed to open nr_fds_wanted file descriptors and