Nathan J. Williams wrote:
 
> There's also:
> 
> (4) make lwp0->l_proc statically point to proc0. This seems like the
>     least-invasive option.
> 
> > I'm not sure what the implications of option (2) are.
> 
> Nor I. What are some MD pre-main() uses of curproc? There's a certain
> sensiblity to leaving the curproc pointer NULL until there is a
> structure with useful data to be pointed to. However, if MD bootstrap
> code is responsible for filling in parts of proc0/lwp0, this could be
> a problem.

ddb seems to be the primary problem here, but I'm not sure there
aren't other subsystems:

sys/arch/alpha/alpha/db_interface.c
sys/arch/mips/mips/trap.c

maybe others...

	-- Gregory McGarry <g.mcgarry@ieee.org>