public inbox for kvm@vger.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 0/2] do not run halted vcpu's
Date: Tue, 19 Aug 2008 20:07:26 -0300	[thread overview]
Message-ID: <20080819230726.GA5157@dmt.cnet> (raw)
In-Reply-To: <48A7D613.5030501@qumranet.com>

On Sun, Aug 17, 2008 at 10:41:07AM +0300, Avi Kivity wrote:
> Avi Kivity wrote:
>> Marcelo Tosatti wrote:
>>> KVM: x86: do not execute halted vcpus
>>>
>>> Alright, need_resched was actually checked in vcpu_enter_guest, so this
>>> checks signal_pending too:
>>>
>>> Offline or uninitialized vcpu's can be executed if requested to perform
>>> userspace work.
>>> Follow Avi's suggestion to handle halted vcpu's in the main loop,
>>> simplifying kvm_emulate_halt(). Introduce a new vcpu->requests bit to
>>> indicate events that promote state from halted to running.
>>>
>>> Also standardize vcpu wake sites.
>>>   
>>
>> Applied, thanks.
>>
>
> This killed reboot, so I reverted it.

Works for me (both UP/SMP, Windows/Linux, guest initiated/system_reset),
and can't find anything obvious in the diff.

How can it be reproduced?


  reply	other threads:[~2008-08-19 23:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 23:09 [patch 0/2] do not run halted vcpu's Marcelo Tosatti
2008-08-01 23:09 ` [patch 1/2] KVM: x86: set debug registers after "schedulable" section Marcelo Tosatti
2008-08-13 10:46   ` Avi Kivity
2008-08-01 23:09 ` [patch 2/2] KVM: x86: do not execute halted vcpus (v2) Marcelo Tosatti
2008-08-13 10:51   ` Avi Kivity
2008-08-13 10:53     ` Avi Kivity
2008-08-13 10:44 ` [patch 0/2] do not run halted vcpu's Avi Kivity
2008-08-15  0:19   ` Marcelo Tosatti
2008-08-17  6:31     ` Avi Kivity
2008-08-17  7:41       ` Avi Kivity
2008-08-19 23:07         ` Marcelo Tosatti [this message]
2008-08-20  4:04           ` 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=20080819230726.GA5157@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox