oops bringing up secondary cpus

Benjamin Herrenschmidt benh at kernel.crashing.org
Sat Jul 17 04:49:14 EST 2004


On Thu, 2004-07-15 at 19:53, Anton Blanchard wrote:
> > OK, but current_set is the task info for the idle process for the new
> > CPU, right?  It looks to me like it's allocated like any old task using
> > copy_process() in smp_create_idle().  This should use kmalloc() like any
> > other task, and that's certainly not guaranteed to be in the RMO.  Did
> > this change recently?  Do we need to lmb_alloc() the idle task struct
> > for the secondary CPUs?
>
> To be honest I cant see where we touch r1 in __secondary_start, have you
> made in changes to it? BTW the rfid at the end of __secondary_start is
> where we go to virtual mode, so you only have to worry about the code
> before that point.

I remember fixing just that bug after paulus rewrite went in, we were
touching the stack before enabling the MMU....

Ben.


** Sent via the linuxppc64-dev mail list. See http://lists.linuxppc.org/





More information about the Linuxppc64-dev mailing list