public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Kechen Lu <kechenl@nvidia.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, vkuznets@redhat.com,
	somduttar@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v3 3/7] KVM: x86: Reject disabling of MWAIT interception when not allowed
Date: Wed, 20 Jul 2022 17:13:42 +0000	[thread overview]
Message-ID: <Ytg3xjZ48w/3Hh6n@google.com> (raw)
In-Reply-To: <20220615011622.136646-4-kechenl@nvidia.com>

On Tue, Jun 14, 2022, Kechen Lu wrote:
> From: Sean Christopherson <seanjc@google.com>
> 
> Reject KVM_CAP_X86_DISABLE_EXITS if userspace attempts to disable MWAIT
> exits and KVM previously reported (via KVM_CHECK_EXTENSION) that MWAIT is
> not allowed in guest, e.g. because it's not supported or the CPU doesn't
> have an aways-running APIC timer.
> 
> Fixes: 4d5422cea3b6 ("KVM: X86: Provide a capability to disable MWAIT intercepts")
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
>  arch/x86/kvm/x86.c | 21 ++++++++++++++-------
>  1 file changed, 14 insertions(+), 7 deletions(-)
> 
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index b419b258ed90..f31ebbb1b94f 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -4199,6 +4199,17 @@ static inline bool kvm_can_mwait_in_guest(void)
>  		boot_cpu_has(X86_FEATURE_ARAT);
>  }
>  
> +static u64 kvm_get_allowed_disable_exits(void)
> +{
> +	u64 r = KVM_X86_DISABLE_EXITS_HLT | KVM_X86_DISABLE_EXITS_PAUSE |
> +		KVM_X86_DISABLE_EXITS_CSTATE;
> +
> +	if(kvm_can_mwait_in_guest())

Probably my fault for not fixing this during copy+paste, but add a space after the if, i.e.

	if (kvm_can_mwait_in_guest())

> +		r |= KVM_X86_DISABLE_EXITS_MWAIT;
> +
> +	return r;
> +}

  reply	other threads:[~2022-07-20 17:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  1:16 [RFC PATCH v3 0/7] KVM: x86: add per-vCPU exits disable capability Kechen Lu
2022-06-15  1:16 ` [RFC PATCH v3 1/7] KVM: x86: only allow exits disable before vCPUs created Kechen Lu
2022-07-20 17:12   ` Sean Christopherson
2022-07-20 17:49     ` Sean Christopherson
2022-07-20 18:38       ` Kechen Lu
2022-06-15  1:16 ` [RFC PATCH v3 2/7] KVM: x86: Move *_in_guest power management flags to vCPU scope Kechen Lu
2022-06-15  1:16 ` [RFC PATCH v3 3/7] KVM: x86: Reject disabling of MWAIT interception when not allowed Kechen Lu
2022-07-20 17:13   ` Sean Christopherson [this message]
2022-06-15  1:16 ` [RFC PATCH v3 4/7] KVM: x86: Let userspace re-enable previously disabled exits Kechen Lu
2022-06-15  2:51   ` Chao Gao
2022-07-20 17:18     ` Sean Christopherson
2022-06-15  1:16 ` [RFC PATCH v3 5/7] KVM: x86: add vCPU scoped toggling for " Kechen Lu
2022-06-15  2:43   ` Chao Gao
2022-06-16  3:04     ` Kechen Lu
2022-07-20 17:38     ` Sean Christopherson
2022-06-15  1:16 ` [RFC PATCH v3 6/7] KVM: x86: Add a new guest_debug flag forcing exit to userspace Kechen Lu
2022-06-15  1:16 ` [RFC PATCH v3 7/7] KVM: selftests: Add tests for VM and vCPU cap KVM_CAP_X86_DISABLE_EXITS Kechen Lu
2022-06-15  3:14   ` Chao Gao
2022-06-15 18:21     ` Kechen Lu

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=Ytg3xjZ48w/3Hh6n@google.com \
    --to=seanjc@google.com \
    --cc=kechenl@nvidia.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=somduttar@nvidia.com \
    --cc=vkuznets@redhat.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