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 CF676C433FE for ; Thu, 27 Oct 2022 00:22:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229691AbiJ0AWQ (ORCPT ); Wed, 26 Oct 2022 20:22:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34788 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233280AbiJ0AWN (ORCPT ); Wed, 26 Oct 2022 20:22:13 -0400 Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0E22589CF8 for ; Wed, 26 Oct 2022 17:22:11 -0700 (PDT) Received: by mail-pl1-x630.google.com with SMTP id g24so10879398plq.3 for ; Wed, 26 Oct 2022 17:22:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=gL9fkvyetCV1Bo4juUosdq663yh2iF/xfOUblLWF8b0=; b=X+ikZz4N8iSORkePbs8KKFAw6/SMc/hBT2Lp36JJJ9UwFAzIffLIbQZ89F7LV1p1Es Zwqb3/KV5EErGZLwLu6c+d55aFsXqcoXQ7a+03+6PNGJECdsNz5S+m6877qEgGMYqedE 9WIbZYu2ZX1eM0ljenU9obLoqtcxafobLUhMzly6BMH18guetLEQ6iJWn56UEIilIl6g KNt/vS94GXjd2tOjWW20jZbB0j79EOQCAxyu6HsBfRZZPD8YuogjVZT4n73cYJJXKWWg PXJ9eQZshqBs2Uh83w+L1EXalXzlZfQFQkBsikDbhHssZFWCg7crwx8gt8YpnJZNPfD1 pIJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to: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=gL9fkvyetCV1Bo4juUosdq663yh2iF/xfOUblLWF8b0=; b=thtS2QZ+7gfbIXXcAxyk/d9iZ4SYPhykKowqSMgKaSLiEqMctM6hOODrU3wJN+Kx+o 5v6HuQGhchJvTrmV5XhAI4rn+jEJz+V/7jpoSu2AROKkDcrgtaUpxP/RK5uBRSsvxxxy 6+eH3QCo19XImOwQZL9kiLhiKUVmLUItfXJc58ENNiaWWGO9uppRu9x90q7RJGGIvGxy 3Vy3NpZ7OOHia9TGSQiudWADe95Q2GrvGLUL8T/RvcEqLhwl+JpPsGu07IP+4bCY94IJ F+iAYZhb0rRxFE3+xGbJpJ1fo0OqvLJXEuBOcMXEmmYSyrTipwdkQP2zmMfndoLpbPoU /mcA== X-Gm-Message-State: ACrzQf0/4ZqLNRCIfo/+QAFzBqi21jJ8RO2CuGrwjn3IiH5wvBKtKqUR i4W+8oxpGlRrSvidWGjIvKd8UQ== X-Google-Smtp-Source: AMsMyM6CD/Y7haI/KExpKQwtJ210I7ZMQY9GjXxFShh03utqVHZJ37k1rcflFBfWHz+H6N05MVxMcQ== X-Received: by 2002:a17:902:e752:b0:186:9efb:71f3 with SMTP id p18-20020a170902e75200b001869efb71f3mr20644688plf.153.1666830130438; Wed, 26 Oct 2022 17:22:10 -0700 (PDT) Received: from google.com (7.104.168.34.bc.googleusercontent.com. [34.168.104.7]) by smtp.gmail.com with ESMTPSA id d8-20020a170902654800b001788ccecbf5sm3472832pln.31.2022.10.26.17.22.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 26 Oct 2022 17:22:09 -0700 (PDT) Date: Thu, 27 Oct 2022 00:22:06 +0000 From: Sean Christopherson To: Wei Wang Cc: pbonzini@redhat.com, dmatlack@google.com, vipinsh@google.com, ajones@ventanamicro.com, eric.auger@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 18/18] KVM: selftests/kvm_create_max_vcpus: check KVM_MAX_VCPUS Message-ID: References: <20221024113445.1022147-1-wei.w.wang@intel.com> <20221024113445.1022147-19-wei.w.wang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221024113445.1022147-19-wei.w.wang@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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".