From: Tao Xu <tao3.xu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Xiaoyao Li <xiaoyao.li@linux.intel.com>,
rkrcmar@redhat.com, corbet@lwn.net, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
sean.j.christopherson@intel.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
fenghua.yu@intel.com, jingqi.liu@intel.com
Subject: Re: [PATCH v5 2/3] KVM: vmx: Emulate MSR IA32_UMWAIT_CONTROL
Date: Wed, 3 Jul 2019 08:29:54 +0800 [thread overview]
Message-ID: <05d4c029-79f4-e513-1778-a7c245a48ad7@intel.com> (raw)
In-Reply-To: <22533924-f7e8-4b50-d5fe-7cbcc9295b53@redhat.com>
On 7/3/2019 12:37 AM, Paolo Bonzini wrote:
> On 20/06/19 11:46, Xiaoyao Li wrote:
>> You cannot put the atomic switch here. What if umwait_control_cached is changed
>> at runtime? Host kernel patch exposed a sysfs interface to let it happen.
>
> Thanks for the review, Xiaoyao. I agree with both of your remarks.
>
> Paolo
>
Hi paolo,
The issues have been solved in v6 patches, could you help to review v6
patches?
Thanks
Tao
>>> + break;
>>> case MSR_IA32_SPEC_CTRL:
>>> if (!msr_info->host_initiated &&
>>> !guest_cpuid_has(vcpu, X86_FEATURE_SPEC_CTRL))
>>> @@ -4126,6 +4148,8 @@ static void vmx_vcpu_reset(struct kvm_vcpu *vcpu, bool
>>> init_event)
>>> vmx->rmode.vm86_active = 0;
>>> vmx->spec_ctrl = 0;
>>>
>>> + vmx->msr_ia32_umwait_control = 0;
>>> +
>>> vcpu->arch.microcode_version = 0x100000000ULL;
>>> vmx->vcpu.arch.regs[VCPU_REGS_RDX] = get_rdx_init_val();
>>> kvm_set_cr8(vcpu, 0);
>>> diff --git a/arch/x86/kvm/vmx/vmx.h b/arch/x86/kvm/vmx/vmx.h
>>> index 61128b48c503..8485bec7c38a 100644
>>> --- a/arch/x86/kvm/vmx/vmx.h
>>> +++ b/arch/x86/kvm/vmx/vmx.h
>>> @@ -14,6 +14,8 @@
>>> extern const u32 vmx_msr_index[];
>>> extern u64 host_efer;
>>>
>>> +extern u32 umwait_control_cached;
>>> +
>>> #define MSR_TYPE_R 1
>>> #define MSR_TYPE_W 2
>>> #define MSR_TYPE_RW 3
>>> @@ -194,6 +196,7 @@ struct vcpu_vmx {
>>> #endif
>>>
>>> u64 spec_ctrl;
>>> + u64 msr_ia32_umwait_control;
>>>
>>> u32 vm_entry_controls_shadow;
>>> u32 vm_exit_controls_shadow;
>>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>>> index 83aefd759846..4480de459bf4 100644
>>> --- a/arch/x86/kvm/x86.c
>>> +++ b/arch/x86/kvm/x86.c
>>> @@ -1138,6 +1138,7 @@ static u32 msrs_to_save[] = {
>>> MSR_IA32_RTIT_ADDR1_A, MSR_IA32_RTIT_ADDR1_B,
>>> MSR_IA32_RTIT_ADDR2_A, MSR_IA32_RTIT_ADDR2_B,
>>> MSR_IA32_RTIT_ADDR3_A, MSR_IA32_RTIT_ADDR3_B,
>>> + MSR_IA32_UMWAIT_CONTROL,
>>> };
>>>
>>> static unsigned num_msrs_to_save;
>>
>
next prev parent reply other threads:[~2019-07-03 0:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 8:46 [PATCH v5 0/3] KVM: x86: Enable user wait instructions Tao Xu
2019-06-20 8:46 ` [PATCH v5 1/3] KVM: x86: add support for " Tao Xu
2019-06-20 13:13 ` Xiaoyao Li
2019-06-20 8:46 ` [PATCH v5 2/3] KVM: vmx: Emulate MSR IA32_UMWAIT_CONTROL Tao Xu
2019-06-20 9:46 ` Xiaoyao Li
2019-07-02 16:37 ` Paolo Bonzini
2019-07-03 0:29 ` Tao Xu [this message]
2019-06-20 10:34 ` Xiaoyao Li
2019-06-20 8:46 ` [PATCH v5 3/3] KVM: vmx: handle vm-exit for UMWAIT and TPAUSE Tao Xu
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=05d4c029-79f4-e513-1778-a7c245a48ad7@intel.com \
--to=tao3.xu@intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jingqi.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=xiaoyao.li@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.