sitter added a comment.
Mh. Please make sure to merge into master as well next time ;)
REPOSITORY
R106 KSysguard
REVISION DETAIL
https://phabricator.kde.org/D8153
To: fvogt, #plasma, sebas
Cc: sitter, plasma-devel, ZrenBot, progwolff, lesliezhai, ali-mohamed,
jensreuterberg, abetts,
This revision was automatically updated to reflect the committed changes.
Closed by commit R106:cbaaf5f4ff54: Try to read CPU clock from
cpufreq/scaling_cur_freq instead of /proc/cpuinfo (authored by fvogt).
REPOSITORY
R106 KSysguard
CHANGES SINCE LAST UPDATE
sebas accepted this revision.
This revision is now accepted and ready to land.
REPOSITORY
R106 KSysguard
BRANCH
Plasma/5.8
REVISION DETAIL
https://phabricator.kde.org/D8153
To: fvogt, #plasma, sebas
Cc: plasma-devel, ZrenBot, progwolff, lesliezhai, ali-mohamed, jensreuterberg,
abetts,
fvogt added a comment.
I could also open all sysfs files only once and then fseek+fscanf when the
value is requested, but that would only exchange a continuous fopen+fclose with
fseek+more complexity IMO.
I'm fine with both approaches, but I favor KISS here.
REPOSITORY
R106 KSysguard
fvogt created this revision.
fvogt added a reviewer: Plasma.
Restricted Application added a project: Plasma.
REVISION SUMMARY
From kernel 4.13 on, /proc/cpuinfo always reports the static normative
CPU clock and not the current one. So try to read the frequency from
cpufreq and only fall
