BCLK is not taken into account for "Top Freq"

[GM-Script-Writer-62850]

Core multiplier * BCLK = Freq BCLK by default is 100 Decent overclocking boards allow the user the change BCLK

i have a core multiplier of 43 and a BCLK of 101.2 (well is is set there, but is acting closer to 101.1712) Anyway this results in Cur Freq > Max Freq Not sure how to handle this or if it is even possible, but this may help the only way i can think of would to be to replace the max freq variable with the cur freq one if it is greater, not a clean way but...

chad@Z97Killer:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq 
4300000
chad@Z97Killer:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq 
800000
chad@Z97Killer:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 
4300000
chad@Z97Killer:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
800000
chad@Z97Killer:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq 
4350362
chad@Z97Killer:~$

Screenshot: https://i.imgur.com/88lJa5Z.png (the fan sensor is showing a 40mm fan) for some reason i can not attach images using firefox...

[amanusk]

At the moment, the max frequency is obtained by reading system information, and looking and what should be the processor top speed (e.g. when using sudo this gives the top Turbo speed when all cores are under stress, this could be lower the top frequency for a single core, so it is possible to see freq > max freq. ) This is unlike all other max stats (power/temperature) where the max value is simply the highest recorded during the session.

Perhaps there should be 2 different metrics, for max freq according to the system and max freq recorded in the session? I am not sure what will be less confusing.

[GM-Script-Writer-62850]

My thought was to update max freq if it ever goes greater unless you have a way to read the bclk, but would a max observed freq be of any use?

[highvoltage]

Not sure if this is related, but a debian user in bug 912783 notes that the maximum frequency in his threadripper is a lot higher than idle and s-tui doesn't seem to take that into account.

[GM-Script-Writer-62850]

Closing this issue as it seems to be resolved in the latest version, well unless you could count the clock speed that is part of the CPU model string (Intel why would you put the clock speed in the model of a K sku product...)

cat /proc/cpuinfo | grep model\ name | head -1
model name  : Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz