kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] Complete cpu initialization before signaling main thread.
Date: Tue, 13 Oct 2009 20:34:21 +0200	[thread overview]
Message-ID: <20091013183421.GC25891@redhat.com> (raw)
In-Reply-To: <20091013182348.GB14313@amt.cnet>

On Tue, Oct 13, 2009 at 03:23:48PM -0300, Marcelo Tosatti wrote:
> On Tue, Oct 13, 2009 at 03:19:08PM -0300, Marcelo Tosatti wrote:
> > > @@ -2003,15 +1991,25 @@ static void *ap_main_loop(void *_env)
> > >          on_vcpu(env, kvm_arch_do_ioperm, data);
> > >  #endif
> > >  
> > > -    /* signal VCPU creation */
> > > +    setup_kernel_sigmask(env);
> > > +
> > >      pthread_mutex_lock(&qemu_mutex);
> > > +    cpu_single_env = env;
> > > +
> > > +    kvm_arch_init_vcpu(env);
> > > +#ifdef TARGET_I386
> > > +    kvm_tpr_vcpu_start(env);
> > > +#endif
> > > +
> > > +    kvm_arch_load_regs(env);
> > > +
> > > +    /* signal VCPU creation */
> > >      current_env->created = 1;
> > >      pthread_cond_signal(&qemu_vcpu_cond);
> > >  
> > >      /* and wait for machine initialization */
> > >      while (!qemu_system_ready)
> > >          qemu_cond_wait(&qemu_system_cond);
> > > -    pthread_mutex_unlock(&qemu_mutex);
> > 
> > You don't set cpu_single_env after reacquiring 
> > qemu_mutex here (via qemu_cond_wait).
> > 
> 
> Also i'm curious about the failure.
This patch by itself doesn't fix the bug. Next one does. This one
rearrange code to make more sense. CPU is created only when it is
initialized and ready to run.

> 
> Why say, bsp should care about other cpu's register state while doing MP
> init?
> 
Because vcpu init will reset MP state, so if bsp will send sipi to vcpu1
before vcpu1 is initialized sipi will be lost.

> MP state is set via apic_reset, which happens before qemu_system_ready
> is set.
> 
Without my next patch MP state is set (by set I mean ioctl(mp_state)) only on vcpu_run.

--
			Gleb.

  reply	other threads:[~2009-10-13 18:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 12:17 [PATCH 1/2] Complete cpu initialization before signaling main thread Gleb Natapov
2009-10-13 12:17 ` [PATCH 2/2] Don't sync mpstate to/from kernel when unneeded Gleb Natapov
2009-10-13 18:36   ` Marcelo Tosatti
2009-10-13 18:40     ` Gleb Natapov
2009-10-13 18:19 ` [PATCH 1/2] Complete cpu initialization before signaling main thread Marcelo Tosatti
2009-10-13 18:23   ` Marcelo Tosatti
2009-10-13 18:34     ` Gleb Natapov [this message]
2009-10-13 18:24   ` Gleb Natapov

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=20091013183421.GC25891@redhat.com \
    --to=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).