From mboxrd@z Thu Jan  1 00:00:00 1970
From: Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: [RFC 0/6] Enlightened VMCS support for KVM on Hyper-V
Date: Tue, 16 Jan 2018 14:58:50 +0100
Message-ID: <87tvvlhplx.fsf@vitty.brq.redhat.com>
References: <20180115173105.31845-1-vkuznets@redhat.com>
        <CANRm+Cza82KuvEQQi=2Zio2u0EHm1kfPfr=aOhoLdra+fpB2Wg@mail.gmail.com>
        <87inc2huux.fsf@vitty.brq.redhat.com>
        <d291d75a-fb19-3f8c-cf73-bcc6bfa82976@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain
Cc: Wanpeng Li <kernellwp@gmail.com>, kvm <kvm@vger.kernel.org>,
        the arch/x86 maintainers <x86@kernel.org>,
        Paolo Bonzini <pbonzini@redhat.com>,
        Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>,
        "K. Y. Srinivasan" <kys@microsoft.com>,
        Haiyang Zhang <haiyangz@microsoft.com>,
        Stephen Hemminger <sthemmin@microsoft.com>,
        "Michael Kelley \(EOSG\)" <Michael.H.Kelley@microsoft.com>,
        Mohammed Gamal <mmorsy@redhat.com>,
        Cathy Avery <cavery@redhat.com>, Bandan Das <bsd@redhat.com>,
        linux-kernel@vger.kernel.org
To: David Hildenbrand <david@redhat.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <d291d75a-fb19-3f8c-cf73-bcc6bfa82976@redhat.com> (David
        Hildenbrand's message of "Tue, 16 Jan 2018 14:39:09 +0100")
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

David Hildenbrand <david@redhat.com> writes:

> On 16.01.2018 13:05, Vitaly Kuznetsov wrote:
>> Wanpeng Li <kernellwp@gmail.com> writes:
>> 
>>> 2018-01-16 1:30 GMT+08:00 Vitaly Kuznetsov <vkuznets@redhat.com>:
>>>> Early RFC. I'll refer to this patchset in my DevConf/FOSDEM
>>>> presentations.
>>>>
>>>> When running nested KVM on Hyper-V it's possible to use so called
>>>> 'Enlightened VMCS' and do normal memory reads/writes instead of
>>>> doing VMWRITE/VMREAD instructions. Tests show that this speeds up
>>>> tight CPUID loop almost 3 times:
>>>>
>>>> Before:
>>>> ./cpuid_tight
>>>> 20459
>>>>
>>>> After:
>>>> ./cpuid_tight
>>>> 7698
>>>
>>> Maybe you can apply a similar idea to kvm nested on kvm.
>>>
>> 
>> Yes we can. Basically, that would mean directly accessing 'struct
>> vmcs12' from L1 hypervisor.
>> 
>
> 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?

-- 
  Vitaly