[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fce01165-912c-a592-2f10-71041ab13b29@redhat.com>
Date: Tue, 16 Jan 2018 15:27:33 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>,
David Hildenbrand <david@...hat.com>
Cc: Wanpeng Li <kernellwp@...il.com>, kvm <kvm@...r.kernel.org>,
the arch/x86 maintainers <x86@...nel.org>,
Radim Krčmář <rkrcmar@...hat.com>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
"Michael Kelley (EOSG)" <Michael.H.Kelley@...rosoft.com>,
Mohammed Gamal <mmorsy@...hat.com>,
Cathy Avery <cavery@...hat.com>, Bandan Das <bsd@...hat.com>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC 0/6] Enlightened VMCS support for KVM on Hyper-V
On 16/01/2018 14:58, Vitaly Kuznetsov wrote:
>> Haven't looked into the details, but we have to watch out for other
>> VCPUs trying to modify that vmcs12.
>>
>> Basically because other VCPUs could try to modify values in vmcs12 while
>> we are currently building vmcs02. Nasty races could result in us copying
>> stuff (probably unchecked) into vmcs02 and therefore running something
>> that was not intended.
>>
> I don't think we share VMCS among vCPUs, do we?
VMCS is just memory, so who knows what a malicious L1 guest will do.
But for vmread/vmwrite we can go through hypervisor memory, for
enlightened VMCS we cannot.
Paolo
Powered by blists - more mailing lists