Re: Porting DTrace to ARM

[Masao Uebayashi <uebayasi%gmail.com@localhost>]

Well, more type is better. :)  See [1].

My question was more like, what happens if CPU can be attached at
run-time in the future?  Per-CPU initialization operations have to be
remembered somewhere.

[1] http://mail-index.netbsd.org/tech-kern/2014/03/03/msg016699.html

On Thu, Mar 6, 2014 at 3:34 PM, Ryota Ozaki <ozaki-r%netbsd.org@localhost> 
wrote:
> On Thu, Mar 6, 2014 at 2:21 PM, Masao Uebayashi 
> <uebayasi%gmail.com@localhost> wrote:
>> Ah.  I misread that schedstate_percpu uses percpu(9)'s fast path,
>> which doesn't exist...
>>
>> Anyway if it's assumed that cpu is not attached at run-time, assigning
>> struct cpu_data::void *cpu_dtraceinfo at module attachment would be
>> just fine.
>
> void * is probably good, otherwise we have to pull out structure definitions
> (ok, there are two: solaris_cpu_t and cpu_core_t) from external/cddl.
> opensolaris_init in external/cddl/osnet/sys/kern/opensolaris.c
> is a good place to assign, I think.
>
> Thanks,
>   ozaki-r