Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp991362imu; Fri, 25 Jan 2019 15:04:05 -0800 (PST) X-Google-Smtp-Source: ALg8bN6yfCPE5JfZ+oYIE+7s0C2xyntoB0oGRTLysJzlzs2J0SlIeb5TdIh7A5YBGThRLsWVWwPD X-Received: by 2002:a17:902:3064:: with SMTP id u91mr12678295plb.325.1548457445651; Fri, 25 Jan 2019 15:04:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548457445; cv=none; d=google.com; s=arc-20160816; b=Bo78gLXzDYnpPWNueHVsEES2OvOnQWrx3x21pnFjNbieSTIDR4vSVG/YYNtcO6GGjP HDexIQzp8RLgZ3Pe/1ecnGZUIH4JC8nG0B7vCnRJM/GAj7bLZoZqbDO2c0JmdPOaGU21 52Nze9g89elMj578gzavQK4muRkPzEgCnrEDUJSaoRahTNthLAE0PtI5EkNOEeQy+HKf nXJ/fAbj/V7+I2j/lU51Qc7FSj6V+BbUlpVlrwnSFx/bOzK82/si6m9FCLQquFEU2yvM trm1GDZNidM23KitL75HOtjASY+OV8fGz0EFzPXLji0FE9ibE6Qw67r3tMLgH98T2EFW BBXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=uQKyANQPZPs4JHRwtSL8hJxjkBeL/g82XuqOyFdO+LY=; b=I012Rw1VNTO/pki5TU6aROsgupqZ8A6gtgLbSL99/Ap09TWyKRxEcvXEN5KdNpLDGo Gi28tFaD1R3jmiCXBEWZvnZaAGprvYsojZptcm8XDsKx8m7xSP5rJfbAkG6dMigmtOIa MhSxEMLZ8lDWEXJNe9IAP2Am7V1SXFAilXRG+2SH8hxNHkYcV605luH+IxLob45L4pbW Z7et3OaeC6RCc4a1b6INu3KjcswIZtUJ4FL4XQoTGV8AlhQrxU/gQbOc0qxF8aPsmgCN Dm07QUO+siq6RxJoyNBN+HdL9Zg/rbEEKULk+KMSrD3ps1SxwzASeJLbMogJDm0pcc+r O+6w== 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 x6si25562364pln.425.2019.01.25.15.03.49; Fri, 25 Jan 2019 15:04:05 -0800 (PST) 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 S1727519AbfAYXDg (ORCPT + 99 others); Fri, 25 Jan 2019 18:03:36 -0500 Received: from mga02.intel.com ([134.134.136.20]:62616 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726179AbfAYXDf (ORCPT ); Fri, 25 Jan 2019 18:03:35 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jan 2019 15:03:34 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,523,1539673200"; d="scan'208";a="141425107" Received: from sjchrist-coffee.jf.intel.com (HELO linux.intel.com) ([10.54.74.14]) by fmsmga001.fm.intel.com with ESMTP; 25 Jan 2019 15:03:34 -0800 Date: Fri, 25 Jan 2019 15:03:34 -0800 From: Sean Christopherson To: Yang Weijiang Cc: pbonzini@redhat.com, rkrcmar@redhat.com, jmattson@google.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, mst@redhat.com, yu-cheng.yu@intel.com, yi.z.zhang@intel.com, hjl.tools@gmail.com, Zhang Yi Z Subject: Re: [PATCH v2 7/7] KVM:X86: Enable MSR_IA32_XSS bit 11 and 12 for CET xsaves/xrstors. Message-ID: <20190125230334.GG21849@linux.intel.com> References: <20190122205909.24165-1-weijiang.yang@intel.com> <20190122205909.24165-8-weijiang.yang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190122205909.24165-8-weijiang.yang@intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 23, 2019 at 04:59:09AM +0800, Yang Weijiang wrote: > For kvm Guest OS, right now, only bit 11(user mode CET) and bit 12 > (supervisor CET) are supported in XSS MSR, if other bits are being set, > the write to XSS will be skipped. > > Signed-off-by: Zhang Yi Z > Signed-off-by: Yang Weijiang > --- > arch/x86/kvm/vmx.c | 11 ++++++++--- > 1 file changed, 8 insertions(+), 3 deletions(-) > > diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c > index 9c8cecac80ea..25ac22b3923a 100644 > --- a/arch/x86/kvm/vmx.c > +++ b/arch/x86/kvm/vmx.c > @@ -47,6 +47,7 @@ > #include > #include > #include > +#include > #include > #include > #include > @@ -4334,12 +4335,16 @@ static int vmx_set_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info) > case MSR_IA32_XSS: > if (!vmx_xsaves_supported()) > return 1; > + > /* > - * The only supported bit as of Skylake is bit 8, but > - * it is not supported on KVM. > + * Right now, only support XSS_CET_U[bit 11] and > + * XSS_CET_S[bit 12] in MSR_IA32_XSS. > */ > - if (data != 0) > + > + if (!vmx_guest_cet_cap(vcpu) || This isn't super intuitive, as evidenced by the additional comment. If you mask off the unsupported bits then you can make a clean check and don't need a comment, e.g.: supported = kvm_supported_xss(); if (!guest_cpuid_has(vcpu, X86_FEATURE_SHSTK) && !guest_cpuid_has(vcpu, X86_FEATURE_IBT)) supported &= ~(XSS_CET_S | XSS_CET_U); if (data & ~supported) return 1; > + data & ~(KVM_SUPPORTED_XSS & host_xss)) Didn't you add kvm_supported_xss() in an earlier patch? Might as well use it here. > return 1; > + > vcpu->arch.ia32_xss = data; > if (vcpu->arch.ia32_xss != host_xss) > add_atomic_switch_msr(vmx, MSR_IA32_XSS, > -- > 2.17.1 >