From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: KVM: x86: do not execute halted vcpus (resend)
Date: Wed, 10 Sep 2008 15:37:16 -0300 [thread overview]
Message-ID: <20080910183716.GA6373@dmt.cnet> (raw)
In-Reply-To: <48C7B7BA.70405@qumranet.com>
On Wed, Sep 10, 2008 at 03:04:10PM +0300, Avi Kivity wrote:
> Avi Kivity wrote:
>> Marcelo Tosatti wrote:
>>> 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.
>>>
>>> Avi, please confirm that this does not break Windows reboot (which I
>>> can't
>>> reproduce).
>>>
>>
>> I couldn't reproduce it either (probably mistested earlier), so I
>> applied it. Sorry about the drops.
>>
>
> Actually it does reproduce. If you reboot twice, the second reboot will
> hang during reset (with cs:ip = f000:fff0). Plain Windows XP.
OK, easily reproducible by adding a sleep at the start of
qemu_kvm_system_reset.
The problem is that the vcpu HLT's between the KBD ioport write and the
actual system reset by the IO thread. By then time there will be no
event that takes it out of STATE_HALTED.
The following fixes it, however older userspace will remain borked.
Alternative is to special case f000:fff0 in-kernel. What is preferred?
diff --git a/libkvm/libkvm.h b/libkvm/libkvm.h
index 346eedf..f3790fa 100644
--- a/libkvm/libkvm.h
+++ b/libkvm/libkvm.h
@@ -330,7 +330,13 @@ int kvm_set_mpstate(kvm_context_t kvm, int vcpu,
*/
static inline int kvm_reset_mpstate(kvm_context_t kvm, int vcpu)
{
- struct kvm_mp_state mp_state = {.mp_state = KVM_MP_STATE_UNINITIALIZED};
+ struct kvm_mp_state mp_state;
+
+ if (vcpu)
+ mp_state.mp_state = KVM_MP_STATE_UNINITIALIZED;
+ else
+ mp_state.mp_state = KVM_MP_STATE_RUNNABLE;
+
return kvm_set_mpstate(kvm, vcpu, &mp_state);
}
#endif
diff --git a/qemu/qemu-kvm-x86.c b/qemu/qemu-kvm-x86.c
index 5daedd1..9983e5a 100644
--- a/qemu/qemu-kvm-x86.c
+++ b/qemu/qemu-kvm-x86.c
@@ -673,15 +673,13 @@ int handle_tpr_access(void *opaque, int vcpu,
void kvm_arch_cpu_reset(CPUState *env)
{
kvm_arch_load_regs(env);
- if (env->cpu_index != 0) {
- if (kvm_irqchip_in_kernel(kvm_context)) {
+ if (kvm_irqchip_in_kernel(kvm_context)) {
#ifdef KVM_CAP_MP_STATE
- kvm_reset_mpstate(kvm_context, env->cpu_index);
+ kvm_reset_mpstate(kvm_context, env->cpu_index);
#endif
- } else {
- env->interrupt_request &= ~CPU_INTERRUPT_HARD;
- env->halted = 1;
- env->exception_index = EXCP_HLT;
- }
+ } else if (env->cpu_index != 0) {
+ env->interrupt_request &= ~CPU_INTERRUPT_HARD;
+ env->halted = 1;
+ env->exception_index = EXCP_HLT;
}
}
next prev parent reply other threads:[~2008-09-10 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 18:23 KVM: x86: do not execute halted vcpus (resend) Marcelo Tosatti
2008-09-09 14:15 ` Avi Kivity
2008-09-10 12:04 ` Avi Kivity
2008-09-10 18:37 ` Marcelo Tosatti [this message]
2008-09-10 18:42 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-09-10 19:40 Marcelo Tosatti
2008-09-11 8:07 ` 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=20080910183716.GA6373@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