Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp2856568ybn; Thu, 26 Sep 2019 19:19:45 -0700 (PDT) X-Google-Smtp-Source: APXvYqyLeeuxq61VvvJYiuANi50qycX5qeYxeMW/Nj8K5CYnwmG+Vxivr4G5Ru6WNH2QYZJCavvC X-Received: by 2002:a50:9e08:: with SMTP id z8mr2083562ede.305.1569550785212; Thu, 26 Sep 2019 19:19:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569550785; cv=none; d=google.com; s=arc-20160816; b=RfJcBP2AAxCdrNLjJoUeBS6mvHRZ/kr7eZPRuXTxoSduHXs/taGNkgqdMJ5angr6rb 8PEcME0JxXsMxlwsZ5I1gAc80qasTbJfCq3PFW3G673uAhWmcL+ohk3zfwquPnx12jkM MfzGdJsVUWaXlb88wa0CeSw3s5Nih4zAKQqCYpf0Kx4zHcgwceqpnhxdckcROMHwwIU4 abm9UsbHzEsYofgWQfyx4bGrIWNRTN/y6Ug8FwKBpwXEBg2tcoZA6yLGIHHtkfj4v9Dv 4VSYpqhLki50XL4SYbPFv68JeYZEIt3zVlZwUnaYKBEfvTmutnu/HZfKWZ6yqLpBJ+H2 jMGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=IuuVfmaJXmb1O38soRTBaCwu3IxACEZqRsDrR9AK3cg=; b=QGaGbIsYhU6LdX8SkP2R7LPYdAM4VU8RinW43qIv44KzwMzpLosXeQy+r5LdjjeTQW GtVIAa2glzONJ8MuwI0C62OXisbx1d28pJ15/A/0eNekVmyMErEwptwBMqXXib/NqFf0 mvHRqniVXXtGoTytNqwI10A+B+xB2ClaOGKYg4baRick1XSGExDzYaMNmmTyB1NRHTYk EK8FLqSGWQDC5mJNI6IHHllY9U1SeDwRh6dRtawOIVI99t+Iqe0qEnuDDUXJTmTYW1kT u9qFbw+4uW0NasycYy0VJ7tnjX4F2T374oH2cku05s9GAgmZPzCCxZOrwWBVgwwnxnWa P9Dw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id fj16si2142747ejb.385.2019.09.26.19.19.19; Thu, 26 Sep 2019 19:19:45 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1728855AbfI0CRU (ORCPT + 99 others); Thu, 26 Sep 2019 22:17:20 -0400 Received: from mga17.intel.com ([192.55.52.151]:25572 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728656AbfI0CRR (ORCPT ); Thu, 26 Sep 2019 22:17:17 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Sep 2019 19:17:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,553,1559545200"; d="scan'208";a="193020675" Received: from unknown (HELO local-michael-cet-test.sh.intel.com) ([10.239.159.128]) by orsmga003.jf.intel.com with ESMTP; 26 Sep 2019 19:17:15 -0700 From: Yang Weijiang To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, pbonzini@redhat.com, sean.j.christopherson@intel.com Cc: mst@redhat.com, rkrcmar@redhat.com, jmattson@google.com, Yang Weijiang Subject: [PATCH v7 4/7] KVM: VMX: Load Guest CET via VMCS when CET is enabled in Guest Date: Fri, 27 Sep 2019 10:19:24 +0800 Message-Id: <20190927021927.23057-5-weijiang.yang@intel.com> X-Mailer: git-send-email 2.17.2 In-Reply-To: <20190927021927.23057-1-weijiang.yang@intel.com> References: <20190927021927.23057-1-weijiang.yang@intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org "Load Guest CET state" bit controls whether Guest CET states will be loaded at Guest entry. Before doing that, KVM needs to check if CPU CET feature is enabled on host and available to Guest. Note: SHSTK and IBT features share one control MSR: MSR_IA32_{U,S}_CET, which means it's difficult to hide one feature from another in the case of SHSTK != IBT, after discussed in community, it's agreed to allow Guest control two features independently as it won't introduce security hole. Co-developed-by: Zhang Yi Z Signed-off-by: Zhang Yi Z Signed-off-by: Yang Weijiang --- arch/x86/kvm/vmx/vmx.c | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c index f720baa7a9ba..ba1a83d11e69 100644 --- a/arch/x86/kvm/vmx/vmx.c +++ b/arch/x86/kvm/vmx/vmx.c @@ -44,6 +44,7 @@ #include #include #include +#include #include "capabilities.h" #include "cpuid.h" @@ -2918,6 +2919,37 @@ void vmx_set_cr3(struct kvm_vcpu *vcpu, unsigned long cr3) vmcs_writel(GUEST_CR3, guest_cr3); } +static int set_cet_bit(struct kvm_vcpu *vcpu, unsigned long cr4) +{ + struct vcpu_vmx *vmx = to_vmx(vcpu); + const u64 cet_bits = XFEATURE_MASK_CET_USER | XFEATURE_MASK_CET_KERNEL; + bool cet_xss = vmx_xsaves_supported() && + (kvm_supported_xss() & cet_bits); + bool cet_cpuid = guest_cpuid_has(vcpu, X86_FEATURE_SHSTK) || + guest_cpuid_has(vcpu, X86_FEATURE_IBT); + bool cet_on = !!(cr4 & X86_CR4_CET); + + if (cet_on && vmx->nested.vmxon) + return 1; + + if (cet_on && !cpu_x86_cet_enabled()) + return 1; + + if (cet_on && !cet_xss) + return 1; + + if (cet_on && !cet_cpuid) + return 1; + + if (cet_on) + vmcs_set_bits(VM_ENTRY_CONTROLS, + VM_ENTRY_LOAD_GUEST_CET_STATE); + else + vmcs_clear_bits(VM_ENTRY_CONTROLS, + VM_ENTRY_LOAD_GUEST_CET_STATE); + return 0; +} + int vmx_set_cr4(struct kvm_vcpu *vcpu, unsigned long cr4) { struct vcpu_vmx *vmx = to_vmx(vcpu); @@ -2958,6 +2990,9 @@ int vmx_set_cr4(struct kvm_vcpu *vcpu, unsigned long cr4) return 1; } + if (set_cet_bit(vcpu, cr4)) + return 1; + if (vmx->nested.vmxon && !nested_cr4_valid(vcpu, cr4)) return 1; -- 2.17.2