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 v2 6/6] KVM: nVMX: optimize prepare_vmcs02{,_full} for Enlightened VMCS case
Date: Wed, 25 Jul 2018 10:37:43 +0200 [thread overview]
Message-ID: <87va93pv6w.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <a826fd88-0199-8e7b-ebfc-290e936b5efc@redhat.com> (Paolo Bonzini's message of "Tue, 24 Jul 2018 19:09:04 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 21/06/2018 14:30, Vitaly Kuznetsov wrote:
>> +static __always_inline bool evmcs_needs_write(struct vcpu_vmx *vmx,
>> + u16 clean_field)
>> +{
>> + if (vmx->nested.dirty_vmcs12)
>> + return true;
>
> Why is this needed? If it weren't for it, you could pass hv_evmcs
> directly to evmcs_needs_write, which would simplify the code a bit in
> the caller.
This is an equivalent of prepare_vmcs02()/prepare_vmcs02_full() split
for eVMCS case: when we switch from L2 guest A to L2 guest B we need to
write the whole VMCS so evmcs_needs_write() needs to return true.
We can, however, make an optimisation: forcefuly reset hv_clean_fields
mask on enlightened vmptrld making 'dirty_vmcs12' check redundant.
This series was posted quite some time ago, I'll rebase and re-test with
the fix included.
Thanks!
--
Vitaly
next prev parent reply other threads:[~2018-07-25 8:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 12:30 [PATCH v2 0/6] KVM: nVMX: Enlightened VMCS for Hyper-V on KVM Vitaly Kuznetsov
2018-06-21 12:30 ` [PATCH v2 1/6] KVM: hyperv: define VP assist page helpers Vitaly Kuznetsov
2018-06-21 12:30 ` [PATCH v2 2/6] KVM: VMX: refactor evmcs_sanitize_exec_ctrls() Vitaly Kuznetsov
2018-06-21 12:30 ` [PATCH v2 3/6] KVM: nVMX: add KVM_CAP_HYPERV_ENLIGHTENED_VMCS capability Vitaly Kuznetsov
2018-06-21 12:30 ` [PATCH v2 4/6] KVM: nVMX: add enlightened VMCS state Vitaly Kuznetsov
2018-06-21 12:30 ` [PATCH v2 5/6] KVM: nVMX: implement enlightened VMPTRLD and VMCLEAR Vitaly Kuznetsov
2018-06-21 12:30 ` [PATCH v2 6/6] KVM: nVMX: optimize prepare_vmcs02{,_full} for Enlightened VMCS case Vitaly Kuznetsov
2018-07-24 17:09 ` Paolo Bonzini
2018-07-25 8:37 ` Vitaly Kuznetsov [this message]
2018-07-25 12:14 ` Paolo Bonzini
2018-07-25 12:50 ` Vitaly Kuznetsov
2018-07-25 12:55 ` Paolo Bonzini
2018-07-25 13:26 ` Vitaly Kuznetsov
2018-07-25 13:31 ` Paolo Bonzini
2018-07-25 14:13 ` Vitaly Kuznetsov
2018-07-25 14:39 ` Paolo Bonzini
2018-07-25 15:19 ` Vitaly Kuznetsov
2018-07-23 11:34 ` [PATCH v2 0/6] KVM: nVMX: Enlightened VMCS for Hyper-V on KVM Vitaly Kuznetsov
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=87va93pv6w.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox