From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Cleanup cpu loop
Date: Mon, 22 Jun 2009 16:41:00 +0300 [thread overview]
Message-ID: <20090622134100.GB15865@redhat.com> (raw)
In-Reply-To: <4A3F878B.9080406@redhat.com>
On Mon, Jun 22, 2009 at 04:30:51PM +0300, Avi Kivity wrote:
> On 06/18/2009 03:22 PM, Gleb Natapov wrote:
>> Rearrange cpu loop to be (hopefully) more readable. Put difference
>> between kernel/userspace irqchip in one place.
>>
>>
>> static void flush_queued_work(CPUState *env)
>> @@ -1877,6 +1871,8 @@ static void update_regs_for_init(CPUState *env)
>> #endif
>>
>> cpu_reset(env);
>> + /* cpu_reset() clears env->halted, cpu should be halted after init */
>> + env->halted = 1;
>>
>
> How does that work for the boot cpu?
void kvm_apic_init(CPUState *env)
{
if (env->cpu_index != 0)
env->kvm_cpu_state.init = 1;
kvm_update_interrupt_request(env);
}
Boot cpu does not get here.
--
Gleb.
prev parent reply other threads:[~2009-06-22 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 12:22 [PATCH] Cleanup cpu loop Gleb Natapov
2009-06-22 13:30 ` Avi Kivity
2009-06-22 13:41 ` Gleb Natapov [this message]
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=20090622134100.GB15865@redhat.com \
--to=gleb@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