All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm@vger.kernel.org
Subject: Re: [patch 1/2] KVM: x86: do not entry guest mode if vcpu is not runnable
Date: Mon, 21 Jul 2008 13:09:02 -0300	[thread overview]
Message-ID: <20080721160902.GA3119@dmt.cnet> (raw)
In-Reply-To: <20080721144037.226624791@localhost.localdomain>

On Mon, Jul 21, 2008 at 11:38:56AM -0300, Marcelo Tosatti wrote:
> If a vcpu has been offlined, or not initialized at all, signals
> requesting userspace work to be performed will result in KVM attempting
> to re-entry guest mode.
> 
> Problem is that the in-kernel irqchip emulation happily executes HALTED
> state vcpu's. This breaks "savevm" on Windows SMP installation (that
> only boots up a single vcpu), for example.
> 
> Fix it by blocking halted vcpu's at kvm_arch_vcpu_ioctl_run(). 
> 
> Change the promotion from halted to running to happen in the vcpu
> context. Use the information available in kvm_vcpu_block(), and the
> current mpstate to make the decision:
> 
> - If there's an in-kernel timer or irq event the halted->running
> promotion evaluation can be performed, no need for userspace assistance.
> 
> - If there's a signal, there's either userspace work to be performed
> in the vcpu's context or irqchip emulation is in userspace.
> 
> This has the nice side effect of avoiding userspace exit in case 
> of irq injection to a halted vcpu from the iothread.
> 
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>

Thinko: reset the vcpu if SIPI received.

BTW, "INIT"/"SIPI" states are x86/IA64 specific MP protocol information,
aren't they? What are they doing in include/linux/ ?


Index: kvm/arch/x86/kvm/x86.c
===================================================================
--- kvm.orig/arch/x86/kvm/x86.c
+++ kvm/arch/x86/kvm/x86.c
@@ -2521,7 +2521,7 @@ int kvm_emulate_halt(struct kvm_vcpu *vc
 		up_read(&vcpu->kvm->slots_lock);
 		ret = kvm_vcpu_block(vcpu);
 		down_read(&vcpu->kvm->slots_lock);
-		if (ret)
+		if (ret || vcpu->arch.mp_state == KVM_MP_STATE_SIPI_RECEIVED)
 			return -EINTR;
 		kvm_vcpu_promote_runnable(vcpu);
 		return 1;

  reply	other threads:[~2008-07-21 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 14:38 [patch 0/2] fix migration/savevm with offline vcpus Marcelo Tosatti
2008-07-21 14:38 ` [patch 1/2] KVM: x86: do not entry guest mode if vcpu is not runnable Marcelo Tosatti
2008-07-21 16:09   ` Marcelo Tosatti [this message]
2008-07-26  8:07   ` Avi Kivity
2008-07-21 14:38 ` [patch 2/2] KVM: x86: standardize vcpu wakeup method for in-kernel irqchip Marcelo Tosatti

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=20080721160902.GA3119@dmt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@qumranet.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 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.