Re: yamt-idlelwp fallout for mips/cobalt?

adnetbsd.org wrote:

> Can you try forcing them into the data segment and see
if that works? Eg:
> 
> struct cpu_info cpu_info_store = { .ci_curlwp =
&lwp0 };
> lwp_t lwp0 = { .l_stat = LSONPROC };

I can't test it right now, but will try later.

> I think cpu_info_store should live somewhere else, like
mips_machdep.c.
> I can have a look once I have 'net connectivity again.

Yes, they are restored in mips_vector_init(), but
in cobalt/machdep.c curcpu() is referred before
mips_vector_init() (though I guess we could defer it).
---
Izumi Tsutsui