Add in system init script for monitoring frequencies.

[GoogleCodeExporter]

I created a system init script which will cause i7z to log out C states, 
temperatures, and frequencies to files on the filesystem, making it easier to 
parse these values and display the data. You can check out the script here: 
https://github.com/rfkrocktk/i7zdaemon

If you'd like to include it in i7z, that'd be great. Apart from that, another 
method (maybe DBus or something similar) would be great to be able to monitor 
specific values for use in software like Conky.

Original issue reported on code.google.com by rfkroc...@gmail.com on 6 Dec 2012 at 5:11

Attachments:

• i7zdaemon

[GoogleCodeExporter]

thanks a lot. i'll look at the code soon and merge it. 

thanks again. I'll keep the issue open till its merged in.

Original comment by abhirana on 11 Dec 2012 at 10:47

• Changed state: Started

[GoogleCodeExporter]

Some of the switches fail with the current SVN.  However I created a script 
called turbo.sh to do some simple calculations based on the above.

However I notice a significant difference between what "cpufreq-info 
-c(0,1,2,3) -fm" reports vs what i7z reports when the CPU is clocked down.

Example:
mpyusko@hal9000:/$ /opt/turbo.sh;cpufreq-info -c0 -fm;cpufreq-info -c1 
-fm;cpufreq-info -c2 -fm;cpufreq-info -c3 -fm;
Turbo Boost: Core1: 2.064GHz Core2: 2.137GHz
1.20 GHz
1.47 GHz
2.00 GHz
1.47 GHz
mpyusko@hal9000:/$

Original comment by mpyu...@gmail.com on 29 Jan 2015 at 10:59

Attachments:

• turbo.sh

[GoogleCodeExporter]

What'd be even better would be to create these values in /sys. That would 
probably mean that i7z would have to operate as a kernel module though...

Original comment by rfkroc...@gmail.com on 29 Jan 2015 at 11:12

[GoogleCodeExporter]

The other issue is the daemon returns two values when the CPU has 4 threads.  

Original comment by mpyu...@gmail.com on 29 Jan 2015 at 11:31

[GoogleCodeExporter]

It directly corresponds only to physical cores, bro. You can't measure the 
temperature or frequency of a core that doesn't physically exist. You can 
isolate which thread lives on which core using values in /sys if you really 
want to. 

Original comment by rfkroc...@gmail.com on 29 Jan 2015 at 11:48