Add support for AMD family 25 (19h) processors in the RAPL component. #275
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Treece-Burgess
added
the
type-feature
Treece-Burgess
force-pushed
the
10.24.24-rapl-amd-families
branch
from
f93bc66 to
05c4aa1
Compare
7 tasks
Tested on Family/Model/Stepping: - 25/1/1 - 25/48/1 - 25/17/1 - 25/144/1 - 25/97/2
Treece-Burgess
force-pushed
the
10.24.24-rapl-amd-families
branch
from
05c4aa1 to
28dd250
Compare
adanalis
approved these changes
Dec 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Description
This PR will add support for AMD Family 25 (19h) in the RAPL component. As a result of this, Issue #141 will be resolved. See commit message or below for Zen 3/Zen 4 model's tested.
Zen 3 Microarchitecture
Zen 3: OACISS - Gilgamesh
papi_native_availpapi_component_availpapi_command_lineZen 3: Oak Ridge - Frontier (Login Node)
papi_native_availpapi_component_availpapi_command_lineZen 3: Oak Ridge - Frontier (Compute Node)
papi_native_availpapi_component_availpapi_command_lineZen 3: ICL - Dopamine
papi_native_availpapi_component_availpapi_command_lineZen 4 Microarchitecture
Zen 4: OACISS - Gary
papi_native_availpapi_component_availpapi_command_lineZen 4: OACISS - Odyssey
papi_native_availpapi_component_availpapi_command_lineZen 4: OACISS - Roberta
papi_native_availpapi_component_availpapi_command_lineZen 4: ICL - Serotonin
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