From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"Roman Kagan" <rkagan@virtuozzo.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>,
linux-kernel@vger.kernel.org, "Jim Mattson" <jmattson@google.com>,
"Liran Alon" <liran.alon@oracle.com>
Subject: Re: [PATCH v3 0/6] KVM: nVMX: Enlightened VMCS for Hyper-V on KVM
Date: Thu, 02 Aug 2018 15:22:44 +0200 [thread overview]
Message-ID: <871sbgaonv.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <4c221ed3-5de8-b9cf-663b-d31ce0834c12@redhat.com> (Paolo Bonzini's message of "Thu, 2 Aug 2018 14:45:10 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 25/07/2018 18:30, Vitaly Kuznetsov wrote:
>> Changes since v2:
>> - Rebase to the current kvm/queue.
>> - Simplify clean fields check in prepare_vmcs02{,_full} and
>> copy_enlightened_to_vmcs12() by resetting the clean fields mask in
>> nested_vmx_handle_enlightened_vmptrld() when we switch from one L2 guest
>> to another [Paolo Bonzini]
>> - Cope with the newly introduced vmx_get_nested_state() by returning
>> -ENOTSUPP when eVMCS is in use. We'll do proper nested state save/restore
>> later.
>
> Looks good, but we have to do something about live migration.
Sure,
I don't actually see any fundumental problems when eVMCS is in use,
however, I'd like to enable migration when we know that it works so I
was going to wait for your nested virtualization state migration series
to land and gain Qemu support before starting to experiment. "One bite
at a time".
> Perhaps you can write a testcase analogous to the new state_test, that
> tests eVMCS in general before we have support in QEMU.
I'll take a look, thanks for the pointer!
--
Vitaly
next prev parent reply other threads:[~2018-08-02 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 16:30 [PATCH v3 0/6] KVM: nVMX: Enlightened VMCS for Hyper-V on KVM Vitaly Kuznetsov
2018-07-25 16:30 ` [PATCH v3 1/6] KVM: hyperv: define VP assist page helpers Vitaly Kuznetsov
2018-07-25 16:30 ` [PATCH v3 2/6] KVM: VMX: refactor evmcs_sanitize_exec_ctrls() Vitaly Kuznetsov
2018-07-25 16:30 ` [PATCH v3 3/6] KVM: nVMX: add KVM_CAP_HYPERV_ENLIGHTENED_VMCS capability Vitaly Kuznetsov
2018-07-25 16:30 ` [PATCH v3 4/6] KVM: nVMX: add enlightened VMCS state Vitaly Kuznetsov
2018-07-25 16:30 ` [PATCH v3 5/6] KVM: nVMX: implement enlightened VMPTRLD and VMCLEAR Vitaly Kuznetsov
2018-07-25 16:30 ` [PATCH v3 6/6] KVM: nVMX: optimize prepare_vmcs02{,_full} for Enlightened VMCS case Vitaly Kuznetsov
2018-08-02 12:45 ` [PATCH v3 0/6] KVM: nVMX: Enlightened VMCS for Hyper-V on KVM Paolo Bonzini
2018-08-02 13:22 ` Vitaly Kuznetsov [this message]
2018-08-02 13:26 ` Paolo Bonzini
2018-08-02 17:25 ` Paolo Bonzini
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=871sbgaonv.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=Michael.H.Kelley@microsoft.com \
--cc=cavery@redhat.com \
--cc=haiyangz@microsoft.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=mmorsy@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkagan@virtuozzo.com \
--cc=rkrcmar@redhat.com \
--cc=sthemmin@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.