From: Sean Christopherson <seanjc@google.com>
To: Kechen Lu <kechenl@nvidia.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, chao.gao@intel.com,
vkuznets@redhat.com, somduttar@nvidia.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v4 5/7] KVM: x86: add vCPU scoped toggling for disabled exits
Date: Wed, 20 Jul 2022 18:41:42 +0000 [thread overview]
Message-ID: <YthMZvWpZ+3gNUhM@google.com> (raw)
In-Reply-To: <20220622004924.155191-6-kechenl@nvidia.com>
On Tue, Jun 21, 2022, Kechen Lu wrote:
> @@ -5980,6 +5987,8 @@ int kvm_vm_ioctl_irq_line(struct kvm *kvm, struct kvm_irq_level *irq_event,
> int kvm_vm_ioctl_enable_cap(struct kvm *kvm,
> struct kvm_enable_cap *cap)
> {
> + struct kvm_vcpu *vcpu;
> + unsigned long i;
> int r;
>
> if (cap->flags)
> @@ -6036,14 +6045,17 @@ int kvm_vm_ioctl_enable_cap(struct kvm *kvm,
> break;
>
> mutex_lock(&kvm->lock);
> - if (kvm->created_vcpus)
> - goto disable_exits_unlock;
> + if (kvm->created_vcpus) {
I retract my comment about using a request, I got ahead of myself.
Don't update vCPUs, the whole point of adding the !kvm->created_vcpus check was
to avoid having to update vCPUs when the per-VM behavior changed.
In other words, keep the restriction and drop the request.
> + kvm_for_each_vcpu(i, vcpu, kvm) {
> + kvm_ioctl_disable_exits(vcpu->arch, cap->args[0]);
> + kvm_make_request(KVM_REQ_DISABLE_EXITS, vcpu);
> + }
> + }
> + mutex_unlock(&kvm->lock);
>
> kvm_ioctl_disable_exits(kvm->arch, cap->args[0]);
>
> r = 0;
> -disable_exits_unlock:
> - mutex_unlock(&kvm->lock);
> break;
> case KVM_CAP_MSR_PLATFORM_INFO:
> kvm->arch.guest_can_read_msr_platform_info = cap->args[0];
> @@ -10175,6 +10187,9 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
>
> if (kvm_check_request(KVM_REQ_UPDATE_CPU_DIRTY_LOGGING, vcpu))
> static_call(kvm_x86_update_cpu_dirty_logging)(vcpu);
> +
> + if (kvm_check_request(KVM_REQ_DISABLE_EXITS, vcpu))
> + static_call(kvm_x86_update_disabled_exits)(vcpu);
> }
>
> if (kvm_check_request(KVM_REQ_EVENT, vcpu) || req_int_win ||
> --
> 2.32.0
>
next prev parent reply other threads:[~2022-07-20 18:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 0:49 [RFC PATCH v4 0/7] KVM: x86: add per-vCPU exits disable capability Kechen Lu
2022-06-22 0:49 ` [RFC PATCH v4 1/7] KVM: x86: only allow exits disable before vCPUs created Kechen Lu
2022-06-22 0:49 ` [RFC PATCH v4 2/7] KVM: x86: Move *_in_guest power management flags to vCPU scope Kechen Lu
2022-06-22 0:49 ` [RFC PATCH v4 3/7] KVM: x86: Reject disabling of MWAIT interception when not allowed Kechen Lu
2022-07-20 17:53 ` Sean Christopherson
2022-07-20 18:37 ` Kechen Lu
2022-06-22 0:49 ` [RFC PATCH v4 4/7] KVM: x86: Let userspace re-enable previously disabled exits Kechen Lu
2022-06-22 0:49 ` [RFC PATCH v4 5/7] KVM: x86: add vCPU scoped toggling for " Kechen Lu
2022-07-20 18:41 ` Sean Christopherson [this message]
2022-07-20 19:04 ` Kechen Lu
2022-07-20 19:30 ` Sean Christopherson
2022-07-20 20:23 ` Kechen Lu
2022-06-22 0:49 ` [RFC PATCH v4 6/7] KVM: x86: Add a new guest_debug flag forcing exit to userspace Kechen Lu
2022-07-20 17:06 ` Sean Christopherson
2022-07-20 19:11 ` Kechen Lu
2022-06-22 0:49 ` [RFC PATCH v4 7/7] KVM: selftests: Add tests for VM and vCPU cap KVM_CAP_X86_DISABLE_EXITS Kechen Lu
2022-06-22 6:44 ` Huang, Shaoqin
2022-06-22 23:30 ` 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=YthMZvWpZ+3gNUhM@google.com \
--to=seanjc@google.com \
--cc=chao.gao@intel.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