Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp92551pxu; Tue, 6 Oct 2020 20:07:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxvMAOMiZsk7+YzSi2J7gbO5oYZZYoElEcRxXELj2NHM90NqycSMWsGaEwYLnsWIHPV2jdM X-Received: by 2002:a17:906:22c1:: with SMTP id q1mr1119963eja.529.1602040062566; Tue, 06 Oct 2020 20:07:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602040062; cv=none; d=google.com; s=arc-20160816; b=ZO57j7sISpvKmEFeD6x+ENgWdPkOvN8Q3O0D2SimFIPKIGWuawNktf8c+mbmnzt+IF MSx0bISAg0jtmD5sy+xHNYiC7p48tD1pSQYYtIlxfj9gbwDT7ppAuWhvvo605jEKwq1M kOrmhMtjurOTIJ4iyi1EJ3/ybSHGtd8/TqMaMFa1A8D/XHipfaGI16x25Kb5ibntKbcq 5Hx/CnOEq1HpizXRpAL8NG1XK76OQ1GaUrCANWjQfItd/MmTDxfhzn7MSF01sQ0W82Go O0hdrHj9fjNddPR+1gNwUiVttP/9fAi4FEqPL0wfLBq5AXYbAkzP3B55yejQsdY5O9Rx tDAA== 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 :ironport-sdr:ironport-sdr; bh=qyETD4BQjaIsKhGYzjkXVl26C3wT2votzaQhkxLqMDQ=; b=fn57GYmqCSneeY/JiROrWOtjEEQUvYChGBq4McwB6AVHwwnVYhfiEMZH/tr8F3jZ/I 8gKJEBy+xgW/QxYwjoQMrwZUEaN76dg43cNVMvj+vTNkmSA3WT0P72fX+5eUKqqKFtMY bWUIVdfyXraPtSQc+k2AIw4aaOrFn67PsCZbfLEC/u0SFTvP+60sP5nkleSjx4Rz5Q0K VcIetc/F9H+V1iVhClezieXU9EXNYKoQc7EvmKQ9GCX9VnAfyo9lsGdTBcHvxgnnyACO /cLwY8MQZXmr+GThoJEw54vC0ZCS2EvxtPByNaEws7nyOjRq9fWbq58tQ1cfJIa3lsX6 Tw9g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l11si505595ejd.105.2020.10.06.20.07.20; Tue, 06 Oct 2020 20:07:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727365AbgJGBoV (ORCPT + 99 others); Tue, 6 Oct 2020 21:44:21 -0400 Received: from mga09.intel.com ([134.134.136.24]:7786 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726323AbgJGBoT (ORCPT ); Tue, 6 Oct 2020 21:44:19 -0400 IronPort-SDR: OQZzdcldT/AWS8dV55KTiw1kOjynNkACiTreEVQmX5tEUz4ZDympu1zekgdIk4WhVo1uIFSuHM J+w2u77omkpw== X-IronPort-AV: E=McAfee;i="6000,8403,9766"; a="164914596" X-IronPort-AV: E=Sophos;i="5.77,344,1596524400"; d="scan'208";a="164914596" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Oct 2020 18:44:18 -0700 IronPort-SDR: vdIVN1gcPV5l+C1riTE0uMgVqZRz19PP8fLkc8NyKxq/zSXAadMYnLp8a/oCbygAnVpLRS/dFO dIxG6y8AWqgw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,344,1596524400"; d="scan'208";a="297410297" Received: from sjchrist-coffee.jf.intel.com ([10.54.74.160]) by fmsmga008.fm.intel.com with ESMTP; 06 Oct 2020 18:44:18 -0700 From: Sean Christopherson To: Paolo Bonzini Cc: Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Stas Sergeev Subject: [PATCH 1/6] KVM: VMX: Drop guest CPUID check for VMXE in vmx_set_cr4() Date: Tue, 6 Oct 2020 18:44:12 -0700 Message-Id: <20201007014417.29276-2-sean.j.christopherson@intel.com> X-Mailer: git-send-email 2.28.0 In-Reply-To: <20201007014417.29276-1-sean.j.christopherson@intel.com> References: <20201007014417.29276-1-sean.j.christopherson@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Drop vmx_set_cr4()'s somewhat hidden guest_cpuid_has() check on VMXE now that common x86 handles the check by incorporating VMXE into the CR4 reserved bits, i.e. in cr4_guest_rsvd_bits. This fixes a bug where KVM incorrectly rejects KVM_SET_SREGS with CR4.VMXE=1 if it's executed before KVM_SET_CPUID{,2}. Fixes: 5e1746d6205d ("KVM: nVMX: Allow setting the VMXE bit in CR4") Reported-by: Stas Sergeev Signed-off-by: Sean Christopherson --- arch/x86/kvm/vmx/vmx.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c index e23c41ccfac9..99ea57ba2a84 100644 --- a/arch/x86/kvm/vmx/vmx.c +++ b/arch/x86/kvm/vmx/vmx.c @@ -3110,9 +3110,10 @@ int vmx_set_cr4(struct kvm_vcpu *vcpu, unsigned long cr4) * must first be able to turn on cr4.VMXE (see handle_vmon()). * So basically the check on whether to allow nested VMX * is here. We operate under the default treatment of SMM, - * so VMX cannot be enabled under SMM. + * so VMX cannot be enabled under SMM. Note, guest CPUID is + * intentionally ignored, it's handled by cr4_guest_rsvd_bits. */ - if (!nested_vmx_allowed(vcpu) || is_smm(vcpu)) + if (!nested || is_smm(vcpu)) return 1; } -- 2.28.0