papi_events.csv: Add preset events support for FUJITSU-MONAKA #277
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
This commit adds preset events support for FUJITSU-MONAKA. Also update arm_cpu_util.c to show the processor name in papi_hardware_avail command.
Yoshihiro-Furudera
force-pushed
the
monaka-support
branch
from
c1b1085
to
894f2ed
Compare
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.
This commit adds present support for FUJITSU-MONAKA.
Also update arm_cpu_util.c to show the processor name in papi_hardware_avail command.
Pull Request Description
Dear papi library development team,
This commit adds present support for FUJITSU-MONAKA.
Also update arm_cpu_util.c to show the processor name in papi_hardware_avail command.
FUJITSU-MONAKA Specification URL:
https://github.com/fujitsu/FUJITSU-MONAKA
Please review and merge these patches
Best regards.
Yoshihiro Furudera
Author 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