All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	Gleb Natapov <gleb@kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] KVM: nVMX: Rework interception of IRQs and NMIs
Date: Fri, 07 Mar 2014 17:46:54 +0100	[thread overview]
Message-ID: <5319F7FE.50106@redhat.com> (raw)
In-Reply-To: <5319F3E2.3020205@siemens.com>

Il 07/03/2014 17:29, Jan Kiszka ha scritto:
> On 2014-03-07 16:44, Paolo Bonzini wrote:
>> With this patch do we still need
>>
>>         if (is_guest_mode(vcpu) && nested_exit_on_intr(vcpu))
>>                 /*
>>                  * We get here if vmx_interrupt_allowed() said we can't
>>                  * inject to L1 now because L2 must run. The caller will have
>>                  * to make L2 exit right after entry, so we can inject to L1
>>                  * more promptly.
>>                  */
>>                 return -EBUSY;
>>
>> in enable_irq_window?  If not, enable_nmi_window and enable_irq_window
>> can both return void.
> 
> I don't see right now why this should have changed. We still cannot
> interrupt vmlaunch/vmresume.

But then shouldn't the ame be true for enable_nmi_window?  It doesn't
check is_guest_mode(vcpu) && nested_exit_on_nmi(vcpu).

Since check_nested_events has already returned -EBUSY, perhaps the
following:

diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index fda1028..df320e9 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -4522,15 +4522,6 @@ static int enable_irq_window(struct kvm_vcpu *vcpu)
 {
 	u32 cpu_based_vm_exec_control;
 
-	if (is_guest_mode(vcpu) && nested_exit_on_intr(vcpu))
-		/*
-		 * We get here if vmx_interrupt_allowed() said we can't
-		 * inject to L1 now because L2 must run. The caller will have
-		 * to make L2 exit right after entry, so we can inject to L1
-		 * more promptly.
-		 */
-		return -EBUSY;
-
 	cpu_based_vm_exec_control = vmcs_read32(CPU_BASED_VM_EXEC_CONTROL);
 	cpu_based_vm_exec_control |= CPU_BASED_VIRTUAL_INTR_PENDING;
 	vmcs_write32(CPU_BASED_VM_EXEC_CONTROL, cpu_based_vm_exec_control);
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index a03d611..83c2df5 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -5970,13 +5970,13 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
 
 		inject_pending_event(vcpu);
 
-		if (is_guest_mode(vcpu) && kvm_x86_ops->check_nested_events)
-			req_immediate_exit |=
-				kvm_x86_ops->check_nested_events(vcpu,
-							req_int_win) != 0;
+		if (is_guest_mode(vcpu) &&
+		    kvm_x86_ops->check_nested_events &&
+		    kvm_x86_ops->check_nested_events(vcpu, req_int_win) != 0)
+			req_immediate_exit = true;
 
 		/* enable NMI/IRQ window open exits if needed */
-		if (vcpu->arch.nmi_pending)
+		else if (vcpu->arch.nmi_pending)
 			req_immediate_exit |=
 				kvm_x86_ops->enable_nmi_window(vcpu) != 0;
                else if (kvm_cpu_has_injectable_intr(vcpu) || req_int_win)


  reply	other threads:[~2014-03-07 16:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 17:33 [PATCH v3 0/3] KVM: x86: Pending nVMX fixes Jan Kiszka
2014-03-06 17:33 ` [PATCH v3 1/3] KVM: nVMX: Rework interception of IRQs and NMIs Jan Kiszka
2014-03-07 15:44   ` Paolo Bonzini
2014-03-07 16:29     ` Jan Kiszka
2014-03-07 16:46       ` Paolo Bonzini [this message]
2014-03-07 17:28         ` Jan Kiszka
2014-03-07 18:19           ` Jan Kiszka
2014-03-07 18:24             ` Paolo Bonzini
2014-03-07 18:26             ` Jan Kiszka
2014-03-07 19:45               ` Paolo Bonzini
2014-03-06 17:33 ` [PATCH v3 2/3] KVM: nVMX: Fully emulate preemption timer Jan Kiszka
2014-03-07 17:20   ` Marcelo Tosatti
2014-03-07 17:24     ` Paolo Bonzini
2014-03-06 17:33 ` [PATCH v3 3/3] KVM: nVMX: Do not inject NMI vmexits when L2 has a pending interrupt Jan Kiszka
2014-03-06 17:41 ` [PATCH v3 0/3] KVM: x86: Pending nVMX fixes Paolo Bonzini

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=5319F7FE.50106@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=gleb@kernel.org \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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 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.