-
Notifications
You must be signed in to change notification settings - Fork 233
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
[FeatureRequest] Graviton 3 support #471
Comments
For a quick fix, you can make V1 look like N1. Yes, SVE counters and others are missing, but this seems to work otherwise:
|
Hi John, I'm currently not happy with the (Could you supply the missing info in #444? Then I could add both architectures in one release.) |
See #472 |
In addition to |
Graviton 3 uses the Neoverse V1 core, so you'll want to use these PMUs instead of the N2 events listed in Issue #444 I admit I have not read both lists and confirmed that they are different :-D |
From a c7g.16xlarge instance (biggest Graviton 3)
|
There seems to be a misunderstanding. #444 should add general support for ARM Neoverse N2. The PR is not related to AWS Graviton 3. I need the For AWS Graviton 3, this info is already encoded in your patch and in PR #472 (topology detection and perf unit). I'll check the event list in the PR to use the V1 list. Providing a general |
AWS Graviton 3 support got merged into the master branch |
Is your feature request related to a problem? Please describe.
Please add Graviton 3 support
Describe the solution you'd like
Commands like
likwid-perfctr -e
should work on Graviton 3:Describe alternatives you've considered
Graviton 2 works great, but I was hoping for Graviton 3 support.
Additional context
Currently, the tool reports Graviton3 as an "Unsupported ARMv8 Processor"
The text was updated successfully, but these errors were encountered: