From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, david@redhat.com,
jmattson@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/3] KVM: nVMX: Emulate EPTP switching for the L1 hypervisor
Date: Tue, 1 Aug 2017 17:17:21 +0200 [thread overview]
Message-ID: <20170801151720.GC302@flask> (raw)
In-Reply-To: <20170728195245.1018-4-bsd@redhat.com>
2017-07-28 15:52-0400, Bandan Das:
> When L2 uses vmfunc, L0 utilizes the associated vmexit to
> emulate a switching of the ept pointer by reloading the
> guest MMU.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Bandan Das <bsd@redhat.com>
> ---
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> @@ -7767,6 +7781,85 @@ static int handle_preemption_timer(struct kvm_vcpu *vcpu)
> return 1;
> }
>
> +static bool check_ept_address_valid(struct kvm_vcpu *vcpu, u64 address)
> +{
> + struct vcpu_vmx *vmx = to_vmx(vcpu);
> + u64 mask = VMX_EPT_RWX_MASK;
> + int maxphyaddr = cpuid_maxphyaddr(vcpu);
> + struct kvm_mmu *mmu = vcpu->arch.walk_mmu;
> +
> + /* Check for execute_only validity */
> + if ((address & mask) == VMX_EPT_EXECUTABLE_MASK) {
> + if (!(vmx->nested.nested_vmx_ept_caps &
> + VMX_EPT_EXECUTE_ONLY_BIT))
> + return false;
> + }
This checks looks wrong ... bits 0:2 define the memory type:
0 = Uncacheable (UC)
6 = Write-back (WB)
If those are supported MSR IA32_VMX_EPT_VPID_CAP, so I think it should
return false when
(address & 0x7) == 0 && !(vmx->nested.nested_vmx_ept_caps & VMX_EPTP_UC_BIT))
the same for 6 and VMX_EPTP_WB_BIT and unconditionally for the remaining
types.
Btw. when is TLB flushed after EPTP switching?
> @@ -10354,10 +10456,20 @@ static int check_vmentry_prereqs(struct kvm_vcpu *vcpu, struct vmcs12 *vmcs12)
> vmx->nested.nested_vmx_entry_ctls_high))
> return VMXERR_ENTRY_INVALID_CONTROL_FIELD;
>
> - if (nested_cpu_has_vmfunc(vmcs12) &&
> - (vmcs12->vm_function_control &
> - ~vmx->nested.nested_vmx_vmfunc_controls))
> - return VMXERR_ENTRY_INVALID_CONTROL_FIELD;
> + if (nested_cpu_has_vmfunc(vmcs12)) {
> + if (vmcs12->vm_function_control &
> + ~vmx->nested.nested_vmx_vmfunc_controls)
> + return VMXERR_ENTRY_INVALID_CONTROL_FIELD;
> +
> + if (nested_cpu_has_eptp_switching(vmcs12)) {
> + if (!nested_cpu_has_ept(vmcs12) ||
> + (vmcs12->eptp_list_address >>
> + cpuid_maxphyaddr(vcpu)) ||
> + !IS_ALIGNED(vmcs12->eptp_list_address, 4096))
page_address_valid() would make this check a bit nicer,
thanks.
> + return VMXERR_ENTRY_INVALID_CONTROL_FIELD;
next prev parent reply other threads:[~2017-08-01 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 19:52 [PATCH v5 0/3] Expose VMFUNC to the nested hypervisor Bandan Das
2017-07-28 19:52 ` [PATCH v5 1/3] KVM: vmx: Enable VMFUNCs Bandan Das
2017-07-28 19:52 ` [PATCH v5 2/3] KVM: nVMX: Enable VMFUNC for the L1 hypervisor Bandan Das
2017-07-28 19:52 ` [PATCH v5 3/3] KVM: nVMX: Emulate EPTP switching " Bandan Das
2017-07-31 11:59 ` David Hildenbrand
2017-07-31 19:32 ` Bandan Das
2017-08-01 11:40 ` David Hildenbrand
2017-08-01 14:55 ` Radim Krčmář
2017-08-01 15:17 ` Radim Krčmář [this message]
2017-08-01 18:30 ` Bandan Das
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=20170801151720.GC302@flask \
--to=rkrcmar@redhat.com \
--cc=bsd@redhat.com \
--cc=david@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox