From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: nVMX: Rename prepare_vmcs02_*_full to prepare_vmcs02_*_extra
Date: Thu, 6 Jun 2019 12:19:04 -0700 [thread overview]
Message-ID: <89dd5d66-0d37-ea41-3f6d-72d5a8a9815d@oracle.com> (raw)
In-Reply-To: <20190606184117.GJ23169@linux.intel.com>
On 06/06/2019 11:41 AM, Sean Christopherson wrote:
> On Thu, Jun 06, 2019 at 05:24:12PM +0200, Paolo Bonzini wrote:
>> These function do not prepare the entire state of the vmcs02, only the
>> rarely needed parts. Rename them to make this clearer.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> arch/x86/kvm/vmx/nested.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
>> index 84438cf23d37..fd8150ef6cce 100644
>> --- a/arch/x86/kvm/vmx/nested.c
>> +++ b/arch/x86/kvm/vmx/nested.c
>> @@ -1955,7 +1955,7 @@ static void prepare_vmcs02_constant_state(struct vcpu_vmx *vmx)
>> vmx_set_constant_host_state(vmx);
>> }
>>
>> -static void prepare_vmcs02_early_full(struct vcpu_vmx *vmx,
>> +static void prepare_vmcs02_early_extra(struct vcpu_vmx *vmx,
> Or maybe 'uncommon', 'rare' or 'ext'? I don't I particularly love any of
> the names, but they're all better than 'full'.
The big chunk of the work in this function is done via
prepare_vmcs02_constant_state(). It seems cleaner to get rid of
prepare_vmcs02_early_full(), call prepare_vmcs02_constant_state()
directly from prepare_vmcs02_early() and move the three vmcs_write16()
calls to prepare_vmcs02_early().
>
> Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>
>
>> struct vmcs12 *vmcs12)
>> {
>> prepare_vmcs02_constant_state(vmx);
>> @@ -1976,7 +1976,7 @@ static void prepare_vmcs02_early(struct vcpu_vmx *vmx, struct vmcs12 *vmcs12)
>> u64 guest_efer = nested_vmx_calc_efer(vmx, vmcs12);
>>
>> if (vmx->nested.dirty_vmcs12 || vmx->nested.hv_evmcs)
>> - prepare_vmcs02_early_full(vmx, vmcs12);
>> + prepare_vmcs02_early_extra(vmx, vmcs12);
>>
>> /*
>> * PIN CONTROLS
>> @@ -2130,7 +2130,7 @@ static void prepare_vmcs02_early(struct vcpu_vmx *vmx, struct vmcs12 *vmcs12)
>> }
>> }
>>
>> -static void prepare_vmcs02_full(struct vcpu_vmx *vmx, struct vmcs12 *vmcs12)
>> +static void prepare_vmcs02_extra(struct vcpu_vmx *vmx, struct vmcs12 *vmcs12)
>> {
>> struct hv_enlightened_vmcs *hv_evmcs = vmx->nested.hv_evmcs;
>>
>> @@ -2254,7 +2254,7 @@ static int prepare_vmcs02(struct kvm_vcpu *vcpu, struct vmcs12 *vmcs12,
>> struct vcpu_vmx *vmx = to_vmx(vcpu);
>>
>> if (vmx->nested.dirty_vmcs12 || vmx->nested.hv_evmcs) {
>> - prepare_vmcs02_full(vmx, vmcs12);
>> + prepare_vmcs02_extra(vmx, vmcs12);
>> vmx->nested.dirty_vmcs12 = false;
>> }
>>
>> --
>> 1.8.3.1
>>
next prev parent reply other threads:[~2019-06-06 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 15:24 Paolo Bonzini
2019-06-06 18:41 ` Sean Christopherson
2019-06-06 19:19 ` Krish Sadhukhan [this message]
2019-06-06 20:19 ` Paolo Bonzini
2019-06-07 12:19 ` Paolo Bonzini
2019-06-07 14:18 ` Sean Christopherson
2019-06-07 15:17 ` Paolo Bonzini
2019-06-07 16:04 ` Sean Christopherson
2019-06-07 16:24 ` 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=89dd5d66-0d37-ea41-3f6d-72d5a8a9815d@oracle.com \
--to=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.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
all inboxes | Powered by JetHome®