Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Intel Alder/Raptor Lake P-cores and E-cores #544

Closed
mlurbe97 opened this issue Apr 28, 2023 · 1 comment
Closed

Intel Alder/Raptor Lake P-cores and E-cores #544

mlurbe97 opened this issue Apr 28, 2023 · 1 comment
Labels

Comments

@mlurbe97
Copy link

mlurbe97 commented Apr 28, 2023

I'm unable to program events on this platforms using the provided function
pcm_c_build_core_event(event_id, event_name)
inside a C code due to there are different events on each type of cores (P and E cores).

Maybe a similar function should be implemented to program events per core
pcm_c_build_core_event_on_core(cpu_id, event_id, event_name)
or a warning should be shown.

Now I'm having 0s on E cores when configuring events for P cores, and viceversa. It could be interesting to monitor similar events on both.

@opcm
Copy link
Contributor

opcm commented May 11, 2023

to program P-cores and E-cores events separately you can try to use a different PCM::program interface with ExtendedCustomCoreEventDescription structure as a parameter:

struct ExtendedCustomCoreEventDescription

It has a separate Atom/E-core event config field:

EventSelectRegister * gpCounterHybridAtomCfg; // general purpose counters for Atom cores in hybrid processors

@intel intel locked and limited conversation to collaborators Nov 20, 2023
@rdementi rdementi converted this issue into discussion #600 Nov 20, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
None yet
Development

No branches or pull requests

3 participants