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
Recently there was a patch (commit
f5b9bdcb530a8871e6c65a617d41001b39bf4912), to fix
resource leak on dir_topology.
Now, the below code segment is either unnecessary or it should call
opendir on 'newpath' instead of 'path'?
dir_topology = opendir(path);
Fix for the below issues -
1. valgrind reports memory leaks in
export_free_gpios. 'line' pointer was never freed.
==5732== 120 bytes in 1 blocks are definitely lost in loss record 130 of 271
==5732==at 0x482CBB8: malloc (vg_replace_malloc.c:270)
==5732==by 0x48CC633: getd
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
Scheduled: June 23, 2014 9:00AM - 11:00AM UTC
Components Affected: releases.linaro.org, snapshots.linaro.org
Description: Scheduled maintenance for releases.linaro.org and
snapshots.linaro.org. We will be updating the Linaro license
production code.
https://bugs.launchpad.net/linaro-license-prote
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
