> > It's a bug in powertop.  The dtrace code that powertop is using
> > aggregates on a processorid_t (cpu) and an uint32_t (cpuspeed).
> >
> > But in function pt_cpufreq_dtrace_walk() the cpu speed is
> > read as uint64_t - this is working with bogus values for cpu
> > speed!
> 
> Thanks, I'll forward this patch to the tesla.
> But it's unrelated with 0% and 100% frequency
> residency.

I've filed CR 6829404 for this issue.
-- 
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to