public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chao Gao <chao.gao@intel.com>
To: Kechen Lu <kechenl@nvidia.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, seanjc@google.com,
	vkuznets@redhat.com, somduttar@nvidia.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v3 5/7] KVM: x86: add vCPU scoped toggling for disabled exits
Date: Wed, 15 Jun 2022 10:43:16 +0800	[thread overview]
Message-ID: <20220615024311.GA7808@gao-cwp> (raw)
In-Reply-To: <20220615011622.136646-6-kechenl@nvidia.com>

>@@ -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) {
>+			kvm_for_each_vcpu(i, vcpu, kvm) {
>+				kvm_ioctl_disable_exits(vcpu->arch, cap->args[0]);
>+				static_call(kvm_x86_update_disabled_exits)(vcpu);

IMO, this won't work on Intel platforms. Because, to manipulate a vCPU's
VMCS, vcpu_load() should be invoked in advance to load the VMCS.
Alternatively, you can add a request KVM_REQ_XXX and defer updating VMCS
to the next vCPU entry.

>+			}
>+		}
>+		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];
>-- 
>2.32.0
>

  reply	other threads:[~2022-06-15  2:43 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
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 [this message]
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=20220615024311.GA7808@gao-cwp \
    --to=chao.gao@intel.com \
    --cc=kechenl@nvidia.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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