All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiaoyao Li <xiaoyao.li@intel.com>
To: "Krish Sadhukhan" <krish.sadhukhan@oracle.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Sean Christopherson" <sean.j.christopherson@intel.com>,
	"Vitaly Kuznetsov" <vkuznets@redhat.com>,
	"Jim Mattson" <jmattson@google.com>,
	"Joerg Roedel" <joro@8bytes.org>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] KVM: VMX: Setup MSR bitmap only when has msr_bitmap capability
Date: Wed, 16 Oct 2019 09:29:38 +0800	[thread overview]
Message-ID: <00aaf6d2-e47c-c972-55b6-c7eedd87a075@intel.com> (raw)
In-Reply-To: <05ff009e-5f60-54ff-a371-111763a1cb7f@oracle.com>

On 10/16/2019 8:40 AM, Krish Sadhukhan wrote:
> 
> 
> On 10/15/2019 09:40 AM, Xiaoyao Li wrote:
>> Move the MSR bitmap setup codes to vmx_vmcs_setup() and only setup them
>> when hardware has msr_bitmap capability.
>>
>> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
>> ---
>>   arch/x86/kvm/vmx/vmx.c | 39 ++++++++++++++++++++-------------------
>>   1 file changed, 20 insertions(+), 19 deletions(-)
>>
>> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
>> index 58b77a882426..7051511c27c2 100644
>> --- a/arch/x86/kvm/vmx/vmx.c
>> +++ b/arch/x86/kvm/vmx/vmx.c
>> @@ -4164,12 +4164,30 @@ static void ept_set_mmio_spte_mask(void)
>>   static void vmx_vmcs_setup(struct vcpu_vmx *vmx)
>>   {
>>       int i;
>> +    unsigned long *msr_bitmap;
>>       if (nested)
>>           nested_vmx_vmcs_setup();
>> -    if (cpu_has_vmx_msr_bitmap())
>> -        vmcs_write64(MSR_BITMAP, __pa(vmx->vmcs01.msr_bitmap));
>> +    if (cpu_has_vmx_msr_bitmap()) {
>> +        msr_bitmap = vmx->vmcs01.msr_bitmap;
>> +        vmx_disable_intercept_for_msr(msr_bitmap, MSR_IA32_TSC, 
>> MSR_TYPE_R);
> 
> vmx_disable_intercept_for_msr() also calls cpu_has_vmx_msr_bitmap(), 
> which means we are repeating the check. A cleaner approach is to remove 
> the call to cpu_has_vmx_msr_bitmap()  from 
> vmx_disable_intercept_for_msr()  and let its callers do the check just 
> like you are doing here.
> 

Right.
I'll improve it. Thanks!

>> +        vmx_disable_intercept_for_msr(msr_bitmap, MSR_FS_BASE, 
>> MSR_TYPE_RW);
>> +        vmx_disable_intercept_for_msr(msr_bitmap, MSR_GS_BASE, 
>> MSR_TYPE_RW);
>> +        vmx_disable_intercept_for_msr(msr_bitmap, MSR_KERNEL_GS_BASE, 
>> MSR_TYPE_RW);
>> +        vmx_disable_intercept_for_msr(msr_bitmap, 
>> MSR_IA32_SYSENTER_CS, MSR_TYPE_RW);
>> +        vmx_disable_intercept_for_msr(msr_bitmap, 
>> MSR_IA32_SYSENTER_ESP, MSR_TYPE_RW);
>> +        vmx_disable_intercept_for_msr(msr_bitmap, 
>> MSR_IA32_SYSENTER_EIP, MSR_TYPE_RW);
>> +        if (kvm_cstate_in_guest(vmx->vcpu.kvm)) {
>> +            vmx_disable_intercept_for_msr(msr_bitmap, 
>> MSR_CORE_C1_RES, MSR_TYPE_R);
>> +            vmx_disable_intercept_for_msr(msr_bitmap, 
>> MSR_CORE_C3_RESIDENCY, MSR_TYPE_R);
>> +            vmx_disable_intercept_for_msr(msr_bitmap, 
>> MSR_CORE_C6_RESIDENCY, MSR_TYPE_R);
>> +            vmx_disable_intercept_for_msr(msr_bitmap, 
>> MSR_CORE_C7_RESIDENCY, MSR_TYPE_R);
>> +        }
>> +
>> +        vmcs_write64(MSR_BITMAP, __pa(msr_bitmap));
>> +    }
>> +    vmx->msr_bitmap_mode = 0;
>>       vmcs_write64(VMCS_LINK_POINTER, -1ull); /* 22.3.1.5 */
>> @@ -6697,7 +6715,6 @@ static struct kvm_vcpu *vmx_create_vcpu(struct 
>> kvm *kvm, unsigned int id)
>>   {
>>       int err;
>>       struct vcpu_vmx *vmx;
>> -    unsigned long *msr_bitmap;
>>       int cpu;
>>       BUILD_BUG_ON_MSG(offsetof(struct vcpu_vmx, vcpu) != 0,
>> @@ -6754,22 +6771,6 @@ static struct kvm_vcpu *vmx_create_vcpu(struct 
>> kvm *kvm, unsigned int id)
>>       if (err < 0)
>>           goto free_msrs;
>> -    msr_bitmap = vmx->vmcs01.msr_bitmap;
>> -    vmx_disable_intercept_for_msr(msr_bitmap, MSR_IA32_TSC, MSR_TYPE_R);
>> -    vmx_disable_intercept_for_msr(msr_bitmap, MSR_FS_BASE, MSR_TYPE_RW);
>> -    vmx_disable_intercept_for_msr(msr_bitmap, MSR_GS_BASE, MSR_TYPE_RW);
>> -    vmx_disable_intercept_for_msr(msr_bitmap, MSR_KERNEL_GS_BASE, 
>> MSR_TYPE_RW);
>> -    vmx_disable_intercept_for_msr(msr_bitmap, MSR_IA32_SYSENTER_CS, 
>> MSR_TYPE_RW);
>> -    vmx_disable_intercept_for_msr(msr_bitmap, MSR_IA32_SYSENTER_ESP, 
>> MSR_TYPE_RW);
>> -    vmx_disable_intercept_for_msr(msr_bitmap, MSR_IA32_SYSENTER_EIP, 
>> MSR_TYPE_RW);
>> -    if (kvm_cstate_in_guest(kvm)) {
>> -        vmx_disable_intercept_for_msr(msr_bitmap, MSR_CORE_C1_RES, 
>> MSR_TYPE_R);
>> -        vmx_disable_intercept_for_msr(msr_bitmap, 
>> MSR_CORE_C3_RESIDENCY, MSR_TYPE_R);
>> -        vmx_disable_intercept_for_msr(msr_bitmap, 
>> MSR_CORE_C6_RESIDENCY, MSR_TYPE_R);
>> -        vmx_disable_intercept_for_msr(msr_bitmap, 
>> MSR_CORE_C7_RESIDENCY, MSR_TYPE_R);
>> -    }
>> -    vmx->msr_bitmap_mode = 0;
>> -
>>       vmx->loaded_vmcs = &vmx->vmcs01;
>>       cpu = get_cpu();
>>       vmx_vcpu_load(&vmx->vcpu, cpu);
> 

  reply	other threads:[~2019-10-16  1:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 16:40 [PATCH 0/4] Refactor vcpu creation flow of x86 arch Xiaoyao Li
2019-10-15 16:40 ` [PATCH 1/4] KVM: VMX: rename {vmx,nested_vmx}_vcpu_setup functions Xiaoyao Li
2019-10-15 22:05   ` Krish Sadhukhan
2019-10-16  1:27     ` Xiaoyao Li
2019-10-16 18:09       ` Krish Sadhukhan
2019-10-17  1:25         ` Xiaoyao Li
2019-10-15 16:40 ` [PATCH 2/4] KVM: VMX: Setup MSR bitmap only when has msr_bitmap capability Xiaoyao Li
2019-10-16  0:40   ` Krish Sadhukhan
2019-10-16  1:29     ` Xiaoyao Li [this message]
2019-10-15 16:40 ` [PATCH 3/4] KVM: X86: Refactor kvm_arch_vcpu_create Xiaoyao Li
2019-10-17 16:12   ` Sean Christopherson
2019-10-15 16:40 ` [PATCH 4/4] KVM: X86: Make vcpu's FPU allocation a common function Xiaoyao 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=00aaf6d2-e47c-c972-55b6-c7eedd87a075@intel.com \
    --to=xiaoyao.li@intel.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=krish.sadhukhan@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=sean.j.christopherson@intel.com \
    --cc=vkuznets@redhat.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.