public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 1/6] KVM: Check for pending events before attempting injection
Date: Wed, 28 Jul 2010 14:22:27 -0300	[thread overview]
Message-ID: <20100728172227.GB26822@amt.cnet> (raw)
In-Reply-To: <4C50608C.7020207@redhat.com>

On Wed, Jul 28, 2010 at 07:53:32PM +0300, Avi Kivity wrote:
>  On 07/28/2010 07:37 PM, Marcelo Tosatti wrote:
> >On Wed, Jul 28, 2010 at 07:31:03PM +0300, Avi Kivity wrote:
> >>  On 07/28/2010 07:21 PM, Marcelo Tosatti wrote:
> >>>On Tue, Jul 27, 2010 at 04:19:35PM +0300, Avi Kivity wrote:
> >>>>Instead of blindly attempting to inject an event before each guest entry,
> >>>>check for a possible event first in vcpu->requests.  Sites that can trigger
> >>>>event injection are modified to set KVM_REQ_EVENT:
> >>>>
> >>>>- interrupt, nmi window opening
> >>>>- ppr updates
> >>>>- i8259 output changes
> >>>>- local apic irr changes
> >>>>- rflags updates
> >>>>- gif flag set
> >>>>- event set on exit
> >>>>
> >>>>This improves non-injecting entry performance, and sets the stage for
> >>>>non-atomic injection.
> >>>>
> >>>>Signed-off-by: Avi Kivity<avi@redhat.com>
> >>>>---
> >>>>  arch/x86/kvm/i8259.c     |    1 +
> >>>>  arch/x86/kvm/lapic.c     |   12 ++++++++++--
> >>>>  arch/x86/kvm/svm.c       |    8 +++++++-
> >>>>  arch/x86/kvm/vmx.c       |    6 ++++++
> >>>>  arch/x86/kvm/x86.c       |   35 ++++++++++++++++++++++++++---------
> >>>>  include/linux/kvm_host.h |    1 +
> >>>>  6 files changed, 51 insertions(+), 12 deletions(-)
> >>>>
> >>>>@@ -4731,17 +4737,19 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
> >>>>  		goto out;
> >>>>  	}
> >>>>
> >>>>-	inject_pending_event(vcpu);
> >>>>+	if (kvm_check_request(KVM_REQ_EVENT, vcpu)) {
> >>>>+		inject_pending_event(vcpu);
> >>>>
> >>>>-	/* enable NMI/IRQ window open exits if needed */
> >>>>-	if (vcpu->arch.nmi_pending)
> >>>>-		kvm_x86_ops->enable_nmi_window(vcpu);
> >>>>-	else if (kvm_cpu_has_interrupt(vcpu) || req_int_win)
> >>>>-		kvm_x86_ops->enable_irq_window(vcpu);
> >>>>+		/* enable NMI/IRQ window open exits if needed */
> >>>>+		if (vcpu->arch.nmi_pending)
> >>>>+			kvm_x86_ops->enable_nmi_window(vcpu);
> >>>>+		else if (kvm_cpu_has_interrupt(vcpu) || req_int_win)
> >>>>+			kvm_x86_ops->enable_irq_window(vcpu);
> >>>Problem is it might not be possible to inject the event signalled by
> >>>KVM_REQ_EVENT, say an interrupt from an irqchip, if there is an event
> >>>that needs reinjection (or an exception).
> >>That can happen event now, no?  A pending exception, interrupt comes
> >>along, injection picks up the exception but leaves the interrupt.
> >>
> >>Now the situation can be more complicated:
> >>
> >>- pending exception
> >>- injection
> >>- interrupt, sets KVM_REQ_EVENT
> >>- notices KVM_REQ_EVENT
> >>- drops KVM_REQ_EVENT, cancels exception (made pending again)
> >>- goes back
> >>- injection (injects exception again, interrupt is pending)
> >>
> >>as far as I can tell, this is all fine.
> >But you cleared KVM_REQ_EVENT. Which means you're not going to inject
> >the pending interrupt on the next entry.
> 
> Doh.  So we need to set KVM_REQ_EVENT again, after the final check
> for vcpu->requests, to make sure we redo injection again.
> 
> So we can make inject_pending_event() return true if there's more in
> the queue, and if it did, re-raise KVM_REQ_EVENT just before entry?

Yeah, that would do it.


  reply	other threads:[~2010-07-28 19:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 13:19 [PATCH 0/6] Nonatomic interrupt injection Avi Kivity
2010-07-27 13:19 ` [PATCH 1/6] KVM: Check for pending events before attempting injection Avi Kivity
2010-07-28 16:21   ` Marcelo Tosatti
2010-07-28 16:31     ` Avi Kivity
2010-07-28 16:37       ` Marcelo Tosatti
2010-07-28 16:53         ` Avi Kivity
2010-07-28 17:22           ` Marcelo Tosatti [this message]
2010-07-29  8:49             ` Avi Kivity
2010-07-29 15:44               ` Marcelo Tosatti
2010-07-29  6:51   ` Gleb Natapov
2010-07-29  8:56     ` Avi Kivity
2010-07-27 13:19 ` [PATCH 2/6] KVM: VMX: Split up vmx_complete_interrupts() Avi Kivity
2010-07-27 13:19 ` [PATCH 3/6] KVM: VMX: Move real-mode interrupt injection fixup to vmx_complete_interrupts() Avi Kivity
2010-07-27 13:19 ` [PATCH 4/6] KVM: VMX: Parameterize vmx_complete_interrupts() for both exit and entry Avi Kivity
2010-07-27 13:19 ` [PATCH 5/6] KVM: Non-atomic interrupt injection Avi Kivity
2010-07-27 13:19 ` [PATCH 6/6] KVM: VMX: Move fixup_rmode_irq() to avoid forward declaration Avi Kivity

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=20100728172227.GB26822@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    /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