Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Jan 2001 22:25:52 -0800
From:      Jason Evans <jasone@canonware.com>
To:        John Baldwin <jhb@FreeBSD.org>
Cc:        Bosko Milekic <bmilekic@FreeBSD.org>, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org
Subject:   Re: cvs commit: src/sys/i386/i386 mp_machdep.c
Message-ID:  <20010127222552.S87569@canonware.com>
In-Reply-To: <XFMail.010127221425.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Sat, Jan 27, 2001 at 10:14:25PM -0800
References:  <200101280341.f0S3f1s35766@freefall.freebsd.org> <XFMail.010127221425.jhb@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 27, 2001 at 10:14:25PM -0800, John Baldwin wrote:
> 
> On 28-Jan-01 Bosko Milekic wrote:
> > bmilekic    2001/01/27 19:41:01 PST
> > 
> >   Modified files:
> >     sys/i386/i386        mp_machdep.c 
> >   Log:
> >   Move the setting of curproc to idleproc up earlier in ap_init(). The
> >   problem is that a mutex lock, prior to this change, is acquired before
> >   the curproc is set to idleproc, so we mess ourselves up by calling
> >   the mutex lock routine with curproc == NULL.
> >   
> >   Moving it up after the aps_ready spin-wait has us hopefully setting it
> >   after idleproc is setup.
> >   
> >   Solved by: jake (the allmighty) :-)
> 
> Forgotten by:   jasone
> 
> Actually, what I suggested to jasone (and kind of preferred myself) was to set
> each curproc in the AP's when we initialized the idleprocs.  This has the
> benefit of being MI:

Actually, I didn't forget it; the machine wouldn't boot with that change in
place, so I took it back out.

Jason


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010127222552.S87569>