[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <41362dc0-a4d5-93ec-848d-193a76a9bd0c@redhat.com>
Date: Tue, 2 Jul 2019 18:30:43 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>, kvm@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
Radim Krčmář <rkrcmar@...hat.com>,
Liran Alon <liran.alon@...cle.com>
Subject: Re: [PATCH v2 0/2] x86/kvm/nVMX: fix Enlightened VMCLEAR
On 28/06/19 13:23, Vitaly Kuznetsov wrote:
> VMCLEAR implementation for Enlightened VMCS is not entirely correct
> when something else than the currently active eVMCS on the calling vCPU
> is targeted. In case there's no currently active eVMCS on the calling vCPU
> we are corrupting the targeted area by writing to the non-existent
> launch_state field.
>
> Fix the logic by always treating the targeted area as 'enlightened' in case
> Enlightened VMEntry is enabled on the calling vCPU.
>
> Changes since v1:
> - 'evmcs_vmptr' -> 'evmcs_gpa' [Paolo Bonzini]
> - avoid nested_release_evmcs() in handle_vmclear even for the currently
> active eVMCS on the calling vCPU [Liran Alon], PATCH1 added to support
> the change.
>
> Vitaly Kuznetsov (2):
> x86/KVM/nVMX: don't use clean fields data on enlightened VMLAUNCH
> x86/kvm/nVMX: fix VMCLEAR when Enlightened VMCS is in use
>
> arch/x86/kvm/vmx/evmcs.c | 18 ++++++++++++++
> arch/x86/kvm/vmx/evmcs.h | 1 +
> arch/x86/kvm/vmx/nested.c | 52 ++++++++++++++++++++++-----------------
> 3 files changed, 49 insertions(+), 22 deletions(-)
>
Queued, thanks.
Paolo
Powered by blists - more mailing lists