rapl: Added RAPL component support for Intel RaptorLake. - #244
Conversation
|
@willowec How many different CPU's in the Intel RaptorLake family were you able to test on for this change and what exactly did you test? It would be good if you could test multiple different CPU's in the Intel RaptorLake family and after building the RAPL component, running the utilities: |
|
@Treece-Burgess I've added the table of tests that I have run, but I only have access to one of the three varieties of RaptorLake machines. I'm glad you pointed this out though, because I when I created this PR I did not know that multiple varieties existed. Would you like me to add the other two varieties without testing them? |
|
@willowec If you could add the other two varieties that would be great! Two other comments:
|
d7eae69 to
295db67
Compare
Add RAPL component support for the RaptorLake architecture. This change was tested for Family/Model/Stepping 0x6/0xb7/0x1 (RaptorLake-S/HX) only. The other two models of RaptorLake (Models 0xba and 0xbf) are untested.
df8aabc to
bf4f484
Compare
Pull Request Description
This PR adds support for the
raplcomponent on Intel's RaptorLake architecture. Adding this was extremely simple as RaptorLake has the same RAPL setup as SandyBridge and IvyBridge.Tested systems:
papi_native_availpapi_component_availpapi_command_lineAuthor Checklist
Why this PR exists. Reference all relevant information, including background, issues, test failures, etc
Commits are self contained and only do one thing
Commits have a header of the form:
module: short descriptionCommits have a body (whenever relevant) containing a detailed description of the addressed problem and its solution
The PR needs to pass all the tests