Aubrey, Here are the details for your second question. > Then, let me check, what you see by issue > # dtrace -l | grep cyclic-start bash-3.2# dtrace -l|grep cyclic-start 5125 sdt genunix cyclic_softint cyclic-start 5126 sdt genunix cyclic_remove_pend cyclic-start 5127 sdt genunix cyclic_expire cyclic-start
Thanks Jitendra Jitendra Sasmal wrote: > Hi Aubrey, >> So I assume the following command line give you nothing, right? >> # dtrace -l | grep cpu_change_speed > Yes, I don't see anything.See below: > bash-3.2# dtrace -l|grep cpu_change_speed > bash-3.2# > > Thanks > Jitendra > Li, Aubrey wrote: >>>> Jitendra Sasmal wrote: >>>> >>>> >>>>> Hi All, >>>>> I build the powertop kernel on my ontario system and rebooted with >>>>> this. Then I tried to compile 'powertop' utility and executed, it >>>>> seems to be working fine except few notes like "C-State Dtrace >>>>> proble not available", "cpu_change_speed Dtrace proble not >>>>> available" etc. >>>>> See attached are the screenshots. >>>>> >>>>> >>>> If you run the powertop kernel on a SPARC system, I would at least >>>> expect the cpu_change_speed DTrace probe to be available, since that >>>> probe is implemented in common/io/cpudrv.c >>>> >>>> >>> I don't see that on sparc system.On sparc it gives the probe is not >>> available. >>> >> >> So I assume the following command line give you nothing, right? >> # dtrace -l | grep cpu_change_speed >> >> Then, let me check, what you see by issue >> # dtrace -l | grep cyclic-start >> >> ? >> >> Thanks, >> -Aubrey >> > >
