-
Notifications
You must be signed in to change notification settings - Fork 480
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
Elkhart Lake Unsupported #830
Comments
Hi Andreas, unfortunately we do not support Elkhart Lake in pcm yet. |
Hi @rdementi, thanks for the clarification. Do you have a raw guess what is needed to add support to this tool? Is there an guide available how to add the a new processor? In general is the processor appending driven by Intel or the community? Thanks for your help. BR, |
Hi Andreas, I see that Elkhart Lake has only core events: https://github.com/intel/perfmon/tree/main/EHL/events therefore the tools/feature support will be limited in PCM, similar to Apollo Lake. Usually the new processor support is added by Intel employees. This case is more difficult because I don't have access to Elkhart Lake. I prepared a debug change re-using some of the Snowridge code because Elkhart Lake has the same Tremont core: Could you please try it and let me know if the pcm utility works? |
Hi @rdementi, the branch https://github.com/intel/pcm/tree/EHL-debug seems to work:
Thanks for adding support. BR, |
Now i tried the tool
For the power tool is the processor still unknown. Would is there also possible to add support for EHL? Thanks & BR, |
Hi Andreas, only the main pcm utility is expected to work on your CPU. Other pcm utilities require special hardware performance monitoring units which are not present in your CPU. |
addressed in 53aab34 |
Thanks for clarification and support. |
Hello Intel,
the tool looks really nice. But when i try to run it on my Intel Atom Elkhart Lake machine i receive following output:
Is the
Elkhart Lake
unsupported by this tool?Thanks for your help.
BR,
Andreas
The text was updated successfully, but these errors were encountered: