mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH (CET v16 26.5)] KVM: x86: Initialize allow_smaller_maxphyaddr earlier in setup
Date: Tue, 23 Sep 2025 14:37:03 +0800	[thread overview]
Message-ID: <cbeaa101-b0fd-49e1-9319-f6070b799214@intel.com> (raw)
In-Reply-To: <20250922184743.1745778-1-seanjc@google.com>

On 9/23/2025 2:47 AM, Sean Christopherson wrote:
> Initialize allow_smaller_maxphyaddr during hardware setup as soon as KVM
> knows whether or not TDP will be utilized.  To avoid having to teach KVM's
> emulator all about CET, KVM's upcoming CET virtualization support will be
> mutually exclusive with allow_smaller_maxphyaddr, i.e. will disable SHSTK
> and IBT if allow_smaller_maxphyaddr is enabled.
> 
> In general, allow_smaller_maxphyaddr should be initialized as soon as
> possible since it's globally visible while its only input is whether or
> not EPT/NPT is enabled.  I.e. there's effectively zero risk of setting
> allow_smaller_maxphyaddr too early, and substantial risk of setting it
> too late.
> 
> Signed-off-by: Sean Christopherson <seanjc@google.com>

Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>

> ---
> 
> As the subject suggests, I'm going to slot this in when applying the CET
> series as this is a dependency for disabling SHSTK and IBT if
> allow_smaller_maxphyaddr.  Without this, SVM will incorrectly clear (or not)
> SHSTK.  VMX isn't affected because !enable_ept disables unrestricted guest,
> which also clears SHSTK and IBT, but as the changelog calls out, there's no
> reason to wait to initialize allow_smaller_maxphyaddr.
> 
> https://lore.kernel.org/all/20250919223258.1604852-28-seanjc@google.com
> 
>   arch/x86/kvm/svm/svm.c | 30 +++++++++++++++---------------
>   arch/x86/kvm/vmx/vmx.c | 16 ++++++++--------
>   2 files changed, 23 insertions(+), 23 deletions(-)
> 
> diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c
> index 54ca0ec5ea57..74a6e3868517 100644
> --- a/arch/x86/kvm/svm/svm.c
> +++ b/arch/x86/kvm/svm/svm.c
> @@ -5413,6 +5413,21 @@ static __init int svm_hardware_setup(void)
>   			  get_npt_level(), PG_LEVEL_1G);
>   	pr_info("Nested Paging %s\n", str_enabled_disabled(npt_enabled));
>   
> +	/*
> +	 * It seems that on AMD processors PTE's accessed bit is
> +	 * being set by the CPU hardware before the NPF vmexit.
> +	 * This is not expected behaviour and our tests fail because
> +	 * of it.
> +	 * A workaround here is to disable support for
> +	 * GUEST_MAXPHYADDR < HOST_MAXPHYADDR if NPT is enabled.
> +	 * In this case userspace can know if there is support using
> +	 * KVM_CAP_SMALLER_MAXPHYADDR extension and decide how to handle
> +	 * it
> +	 * If future AMD CPU models change the behaviour described above,
> +	 * this variable can be changed accordingly
> +	 */
> +	allow_smaller_maxphyaddr = !npt_enabled;
> +
>   	/* Setup shadow_me_value and shadow_me_mask */
>   	kvm_mmu_set_me_spte_mask(sme_me_mask, sme_me_mask);
>   
> @@ -5492,21 +5507,6 @@ static __init int svm_hardware_setup(void)
>   
>   	svm_set_cpu_caps();
>   
> -	/*
> -	 * It seems that on AMD processors PTE's accessed bit is
> -	 * being set by the CPU hardware before the NPF vmexit.
> -	 * This is not expected behaviour and our tests fail because
> -	 * of it.
> -	 * A workaround here is to disable support for
> -	 * GUEST_MAXPHYADDR < HOST_MAXPHYADDR if NPT is enabled.
> -	 * In this case userspace can know if there is support using
> -	 * KVM_CAP_SMALLER_MAXPHYADDR extension and decide how to handle
> -	 * it
> -	 * If future AMD CPU models change the behaviour described above,
> -	 * this variable can be changed accordingly
> -	 */
> -	allow_smaller_maxphyaddr = !npt_enabled;
> -
>   	kvm_caps.inapplicable_quirks &= ~KVM_X86_QUIRK_CD_NW_CLEARED;
>   	return 0;
>   
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index 509487a1f04a..ace8208fc1be 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -8479,6 +8479,14 @@ __init int vmx_hardware_setup(void)
>   		return -EOPNOTSUPP;
>   	}
>   
> +	/*
> +	 * Shadow paging doesn't have a (further) performance penalty
> +	 * from GUEST_MAXPHYADDR < HOST_MAXPHYADDR so enable it
> +	 * by default
> +	 */
> +	if (!enable_ept)
> +		allow_smaller_maxphyaddr = true;
> +
>   	if (!cpu_has_vmx_ept_ad_bits() || !enable_ept)
>   		enable_ept_ad_bits = 0;
>   
> @@ -8715,14 +8723,6 @@ int __init vmx_init(void)
>   
>   	vmx_check_vmcs12_offsets();
>   
> -	/*
> -	 * Shadow paging doesn't have a (further) performance penalty
> -	 * from GUEST_MAXPHYADDR < HOST_MAXPHYADDR so enable it
> -	 * by default
> -	 */
> -	if (!enable_ept)
> -		allow_smaller_maxphyaddr = true;
> -
>   	return 0;
>   
>   err_l1d_flush:
> 
> base-commit: d44fa096b63659f2398a28f24d99e48c23857c82


      reply	other threads:[~2025-09-23  6:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 18:47 Sean Christopherson
2025-09-23  6:37 ` Xiaoyao Li [this message]

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=cbeaa101-b0fd-49e1-9319-f6070b799214@intel.com \
    --to=xiaoyao.li@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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®