kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Yang Zhang <yang.zhang.wz@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	Jim Mattson <jmattson@google.com>,
	Wincy Van <fanwenyi0529@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Bandan Das <bsd@redhat.com>
Subject: Re: [PATCH 1/2] KVM: nVMX: fix msr bitmaps to prevent L2 from accessing L0 x2APIC
Date: Tue, 9 Aug 2016 14:23:20 +0200	[thread overview]
Message-ID: <20160809122319.GA2607@potion> (raw)
In-Reply-To: <a7367ae6-9610-290f-22bd-e5272bdc32ef@gmail.com>

2016-08-09 17:32+0800, Yang Zhang:
> On 2016/8/9 2:16, Radim Krčmář wrote:
>> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
>> @@ -6995,16 +6982,21 @@ static int handle_vmon(struct kvm_vcpu *vcpu)
>>  		return 1;
>>  	}
>> 
>> +	if (cpu_has_vmx_msr_bitmap()) {
>> +		vmx->nested.msr_bitmap =
>> +				(unsigned long *)__get_free_page(GFP_KERNEL);
>> +		if (!vmx->nested.msr_bitmap)
>> +			goto out_msr_bitmap;
>> +	}
>> +
> 
> We export msr_bitmap to guest even it is not supported by hardware. So we
> need to allocate msr_bitmap for L1 unconditionally.

We do emulate the feature, but the vmx->nested.msr_bitmap is used only
if VMX supports it to avoid some VM exits:

>> @@ -9957,10 +9938,10 @@ static void prepare_vmcs02(struct kvm_vcpu *vcpu, struct vmcs12 *vmcs12)
>>  	}
>> 
>>  	if (cpu_has_vmx_msr_bitmap() &&
>> -	    exec_control & CPU_BASED_USE_MSR_BITMAPS) {
>> -		nested_vmx_merge_msr_bitmap(vcpu, vmcs12);
>> -		/* MSR_BITMAP will be set by following vmx_set_efer. */
>> -	} else
>> +	    exec_control & CPU_BASED_USE_MSR_BITMAPS &&
>> +	    nested_vmx_merge_msr_bitmap(vcpu, vmcs12))
>> +		; /* MSR_BITMAP will be set by following vmx_set_efer. */
>> +	else
>>  		exec_control &= ~CPU_BASED_USE_MSR_BITMAPS;

The else branch is taken if !cpu_has_vmx_msr_bitmap() and disables msr
bitmaps.  Similar check for vmx_set_msr_bitmap(), so the NULL doesn't
even get written to VMCS.

KVM always uses L1's msr bitmaps when emulating the feature.

  parent reply	other threads:[~2016-08-09 12:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 18:16 [PATCH 0/2] KVM: nVMX: msr bitmaps fixes Radim Krčmář
2016-08-08 18:16 ` [PATCH 1/2] KVM: nVMX: fix msr bitmaps to prevent L2 from accessing L0 x2APIC Radim Krčmář
2016-08-09  9:32   ` Yang Zhang
2016-08-09 10:19     ` Wincy Van
2016-08-10  5:52       ` Yang Zhang
2016-08-09 12:23     ` Radim Krčmář [this message]
2016-08-10  5:55       ` Yang Zhang
2016-08-16  2:53   ` Wanpeng Li
2016-08-08 18:16 ` [PATCH 2/2] KVM: nVMX: postpone VMCS changes on MSR_IA32_APICBASE write Radim Krčmář
2016-08-12  6:07   ` Wanpeng Li
2016-08-12  9:44     ` Radim Krčmář
2016-08-12 10:14       ` Wanpeng Li
2016-08-12 11:39         ` Radim Krčmář
2016-08-15  5:19           ` Wanpeng Li
2016-08-15 14:31             ` Radim Krčmář
2016-08-16  2:43   ` 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=20160809122319.GA2607@potion \
    --to=rkrcmar@redhat.com \
    --cc=bsd@redhat.com \
    --cc=fanwenyi0529@gmail.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=yang.zhang.wz@gmail.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;
as well as URLs for NNTP newsgroup(s).