-
Notifications
You must be signed in to change notification settings - Fork 59
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
RAPL not working on Intel i7-10700T #276
Comments
Hello @hauensj1, on the Intel I7-10700T can you send me the output for |
Following up with this. |
@Treece-Burgess Sorry for the delay. I was not back in the office until today. I've attached the output from This is output from PAPI 6.0.0.1, because that is the library I was using on the machine at this time, but the status is the same in the latest PAPI 7 release (at least, as of a few weeks ago, when I last checked): it reports that the CPU model is not supported unless modified. |
Hello @hauensj1 thank you for sending that to me! I hope you are having a good holiday season. I have created PR #294 which will add support for Intel Comet Lake S/H for the RAPL component. I do not have access as of now to a machine that has an Intel Comet Lake S/H for testing and we would like to test before merging. Would you be able to checkout the PR and test the RAPL component with this addition? After building PAPI, testing would include:
Along with running the tests, if you could send the output for each that would be great! |
@hauensj1 I just wanted to follow up with this. |
papi_component_avail reports that the RAPL component is not usable on Intel i7-10700T processor with an error of "CPU model not supported".
Digging into the code, it appears as though this Comet Lake chip returns a cpuid_model value of 165, which isn't matched by any of the switch cases in linux-rapl.c. Adding a case for 165 and having it fall through to the existing case 158 (Kabylake) code appears to (probably) work. At least, numbers are returned for the energy measurements now, and they look vaguely correct.
The text was updated successfully, but these errors were encountered: