Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: Getting incorrect max frequency value #745

Closed
wants to merge 3 commits into from

Conversation

LDrawe
Copy link

@LDrawe LDrawe commented Jul 18, 2024

This PR (partially) closes #737. Instead of getting the max frequency from cpuinfo_max_freq, it gets from scaling_max_freq. It shoudn't be a problem for most systems, since these values tend to be the same. However, on some cases(like #737), they are reported different, with the scaling_max_freq being the correct one. Apparently this can happen if turbo boost is enabled by means other than the bios , like writing to the cpu registers directly or editing /sys/devices/system/cpu/intel_pstate/no_turbo

Any feedback about potential problems or improvements would be greatly appreciated.

@LDrawe LDrawe closed this Jul 21, 2024
@LDrawe
Copy link
Author

LDrawe commented Jul 21, 2024

Closing this for now, as of yesterday I started getting mixed results, will investigate futher to see what's actually going on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Not detecting correct CPU Max frequency and ignoring config file
1 participant