Vince Weaver
unread,Mar 8, 2024, 1:12:20 AM3/8/24Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Vince Weaver, Heike Jagode, Stephane Eranian, Anuraag Nandi, ptools-perfapi, Rongcui, Giuseppe Congiu
Further investigating this on a Raptor Lake machine, it turns out the
problem is PAPI will get confused in pe_libpfm4_events.c if more
than one PFM_PMU_TYPE_CORE pmu is found.
If you comment out the "return PAPI_ECOUNT" error, papi will return native
events fine, but due to the probing order will treat the E-core (adl_grt)
cores as the default pmu and the P-cores as a secondary one. Which is
probaly the opposite of the default we want but not sure if there's a good
way to fix that without hard-coding the pmu names in there (though maybe
we already do something similar for zen1).
That could maybe be an OK short term fix.
A longer term issue is how to handle things like PAPI_TOT_CYC on a machine
with both P and E cores. Should it be a derived event that adds up the P
and E cycle counts?
Vince
and of course in the previous message I meant ice lake (icl) there, not
cascade lake. too many lakes in intel chips.
Vince Weaver
vincent...@maine.edu
Associate Professor, Electrical and Computer Engineering
http://web.eece.maine.edu/~vweaver/