All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Shiyuan Gao <gaoshiyuan@baidu.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	x86@kernel.org, pbonzini@redhat.com, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	hpa@zytor.com
Subject: Re: [PATCH] KVM: VMX: Rename vmx_get_max_tdp_level to vmx_get_max_ept_level
Date: Mon, 14 Aug 2023 11:14:14 -0700	[thread overview]
Message-ID: <ZNpu9qJOqLxG5pq4@google.com> (raw)
In-Reply-To: <20230810113853.98114-1-gaoshiyuan@baidu.com>

On Thu, Aug 10, 2023, Shiyuan Gao wrote:
> In vmx, ept_level looks better than tdp level and is consistent with
> svm get_npt_level().
> 
> Signed-off-by: Shiyuan Gao <gaoshiyuan@baidu.com>
> ---
>  arch/x86/kvm/vmx/vmx.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index df461f387e20..f0cfd1f10a06 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -3350,7 +3350,7 @@ void vmx_set_cr0(struct kvm_vcpu *vcpu, unsigned long cr0)
>  	vmx->emulation_required = vmx_emulation_required(vcpu);
>  }
>  
> -static int vmx_get_max_tdp_level(void)
> +static int vmx_get_max_ept_level(void)
>  {
>  	if (cpu_has_vmx_ept_5levels())
>  		return 5;
> @@ -8526,7 +8526,7 @@ static __init int hardware_setup(void)
>  	 */
>  	vmx_setup_me_spte_mask();
>  
> -	kvm_configure_mmu(enable_ept, 0, vmx_get_max_tdp_level(),
> +	kvm_configure_mmu(enable_ept, 0, vmx_get_max_ept_level(),
>  			  ept_caps_to_lpage_level(vmx_capability.ept));

Anyone else have an opinion on this?  I'm leaning toward applying it, but a small
part of me also kinda likes the "tdp" name (though every time I look at this patch
that part of me gets even smaller...).

  reply	other threads:[~2023-08-14 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 11:38 [PATCH] KVM: VMX: Rename vmx_get_max_tdp_level to vmx_get_max_ept_level Shiyuan Gao
2023-08-14 18:14 ` Sean Christopherson [this message]
2023-08-15  7:56   ` Gao,Shiyuan
2023-08-18  0:13 ` Sean Christopherson

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=ZNpu9qJOqLxG5pq4@google.com \
    --to=seanjc@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gaoshiyuan@baidu.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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.