Can you try changing your workload?
On Fri, Jun 20, 2014 at 4:57 PM, Salman Ahmed wrote:
> I tried 10 times running 15 seconds and out of that 3 times I got output
> without any P-state information.
>
> --
> Thanks,
> Salman Ahmed
>
>
>
> On Friday, 20 June 2014, 16:49, Amit Kucheria
> wrote:
I tried 10 times running 15 seconds and out of that 3 times I got output
without any P-state information.
--
Thanks,
Salman Ahmed
On Friday, 20 June 2014, 16:49, Amit Kucheria wrote:
On Fri, Jun 20, 2014 at 4:01 PM, Salman Ahmed wrote:
> Hello Amit,
>
> Actually, I ran it on the same m
On Fri, Jun 20, 2014 at 4:01 PM, Salman Ahmed wrote:
> Hello Amit,
>
> Actually, I ran it on the same machine with the same command again and these
> time the output has frequency information-
>
> $ sudo ./idlestat --trace -t 5 -f /tmp/myoutput -- top
>
> Log is 4.999547 secs long with 710 events
Hello Amit,
Actually, I ran it on the same machine with the same command again and these
time the output has frequency information-
$ sudo ./idlestat --trace -t 5 -f /tmp/myoutput -- top
Log is 4.999547 secs long with 710 events
clusterA@state hits total(us) avg(us) min(us) m
I am running it on Intel x86 platform and the output of 'cat
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies' is
3101000 310 280 260 240 220 200 180 160
--Thanks,
Salman
On Friday, 20 June 2014, 10:26, Amit Kucheria wrote:
On Fri, Jun 20,
On Fri, Jun 20, 2014 at 9:47 AM, Salman Ahmed wrote:
> Hello Amit,
>
> I have pulled changes and run with your suggested following command
> sudo ./idlestat --trace -t 5 -f /tmp/myoutput -- top
>
> But still it came up with the output without any frequency information.
What platform are you runni
Hello Amit,
I have pulled changes and run with your suggested following command
sudo ./idlestat --trace -t 5 -f /tmp/myoutput -- top
But still it came up with the output without any frequency information.
Total trace buffer: 153896 kB
Log is 4.999537 secs long with 702 events
clusterA@stat
Hi Salman,
On Thu, Jun 19, 2014 at 1:36 PM, Salman Ahmed wrote:
> Hello,
> Running top command with idlestat tool doesn't show any frequency
> information sometimes. I have run the program with the following
> command -
> # sudo idlestat --trace -t 5 -f /tmp/myoutput /usr/bin/top
> and it ended u
Hello,
Running top command with idlestat tool doesn't show any frequency
information sometimes. I have run the program with the following
command -
#sudo idlestat --trace -t 5 -f /tmp/myoutput /usr/bin/top
and it ended up with the following output where there is no frequency
state information
