From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wanpeng Li <kernellwp@gmail.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Sean Christopherson" <sean.j.christopherson@intel.com>,
"Liran Alon" <liran.alon@oracle.com>
Subject: Re: [PATCH] KVM: X86: Enable IA32_MSIC_ENABLE MONITOR bit when exposing mwait/monitor
Date: Mon, 13 May 2019 07:22:32 -0400 [thread overview]
Message-ID: <0F74F27F-2403-441D-8702-373BDA21E3A7@oracle.com> (raw)
In-Reply-To: <1557740799-5792-1-git-send-email-wanpengli@tencent.com>
On May 13, 2019 5:46:39 AM EDT, Wanpeng Li <kernellwp@gmail.com> wrote:
>From: Wanpeng Li <wanpengli@tencent.com>
>
>MSR IA32_MSIC_ENABLE bit 18, according to SDM:
>
MSIC? (Also the $subject)
>| When this bit is set to 0, the MONITOR feature flag is not set
>(CPUID.01H:ECX[bit 3] = 0).
> | This indicates that MONITOR/MWAIT are not supported.
> |
>| Software attempts to execute MONITOR/MWAIT will cause #UD when this
>bit is 0.
> |
>| When this bit is set to 1 (default), MONITOR/MWAIT are supported
>(CPUID.01H:ECX[bit 3] = 1).
>
>This bit should be set to 1, if BIOS enables MONITOR/MWAIT support on
>host and
>we intend to expose mwait/monitor to the guest.
>
>Cc: Paolo Bonzini <pbonzini@redhat.com>
>Cc: Radim Krčmář <rkrcmar@redhat.com>
>Cc: Sean Christopherson <sean.j.christopherson@intel.com>
>Cc: Liran Alon <liran.alon@oracle.com>
>Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
>---
> arch/x86/kvm/x86.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
>diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>index 1d89cb9..664449e 100644
>--- a/arch/x86/kvm/x86.c
>+++ b/arch/x86/kvm/x86.c
>@@ -2723,6 +2723,13 @@ static int get_msr_mce(struct kvm_vcpu *vcpu,
>u32 msr, u64 *pdata, bool host)
> return 0;
> }
>
>+static inline bool kvm_can_mwait_in_guest(void)
>+{
>+ return boot_cpu_has(X86_FEATURE_MWAIT) &&
>+ !boot_cpu_has_bug(X86_BUG_MONITOR) &&
>+ boot_cpu_has(X86_FEATURE_ARAT);
>+}
>+
>int kvm_get_msr_common(struct kvm_vcpu *vcpu, struct msr_data
>*msr_info)
> {
> switch (msr_info->index) {
>@@ -2801,6 +2808,8 @@ int kvm_get_msr_common(struct kvm_vcpu *vcpu,
>struct msr_data *msr_info)
> msr_info->data = (u64)vcpu->arch.ia32_tsc_adjust_msr;
> break;
> case MSR_IA32_MISC_ENABLE:
>+ if (kvm_can_mwait_in_guest() && kvm_mwait_in_guest(vcpu->kvm))
>+ vcpu->arch.ia32_misc_enable_msr |= MSR_IA32_MISC_ENABLE_MWAIT;
> msr_info->data = vcpu->arch.ia32_misc_enable_msr;
> break;
> case MSR_IA32_SMBASE:
>@@ -2984,13 +2993,6 @@ static int msr_io(struct kvm_vcpu *vcpu, struct
>kvm_msrs __user *user_msrs,
> return r;
> }
>
>-static inline bool kvm_can_mwait_in_guest(void)
>-{
>- return boot_cpu_has(X86_FEATURE_MWAIT) &&
>- !boot_cpu_has_bug(X86_BUG_MONITOR) &&
>- boot_cpu_has(X86_FEATURE_ARAT);
>-}
>-
> int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
> {
> int r = 0;
next prev parent reply other threads:[~2019-05-13 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 9:46 Wanpeng Li
2019-05-13 11:22 ` Konrad Rzeszutek Wilk [this message]
2019-05-13 13:35 ` Radim Krčmář
2019-05-14 6:13 ` Wanpeng Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0F74F27F-2403-441D-8702-373BDA21E3A7@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®