cpu support about numap

[trahay]

From the documentation, it looks like Xeon Phi only has a limited support for PEBS, and it does not include the events that would be needed by numap.
Could you send me the output of perf list so that I can see the list of available events on your machine ?

[cycyyy]

“MEM_UOPS_RETIRED
• Event Select: 4h
• Event Description: Counts the number of memory micro-ops retired. Prefetches
will not be counted.”
I read this event in the doc.

I also get
" mem_uops_retired.all_loads
[Counts all the load micro-ops retired]
mem_uops_retired.all_stores
[Counts all the store micro-ops retired]"
in my perf list.
Does it work for numap?
It seems Xeon Phi don't have L3 cache @trahay

And here is a event i print by using PAPI

[trahay]

I pushed a new branch (xeon_phi) that adds these events for xeon phi. I could not test it, so please let me know if it works for you.

[ManuelSelva]

I pushed a new branch (xeon_phi) that adds these events for xeon phi. I could not test it, so please let me know if it works for you.

François, does this event supports PEBS ?

[trahay]

@ManuelSelva I'm not sure (that's why i pushed it on a new branch). On some architectures, there are some "mem_trans_retired;all_stores events" in PEBS, so these events may be from PEBS

[ManuelSelva]

@trahay Ok I understand now. Thank you very much for the support and let's wait for @cycyyy try on the actual machine to see if it works.

[cycyyy]

I tested on my server and it's cause the "Segmentation fault".
I also asked the professor and he said that xeon_phi hasn't supported for PEBS now so that it couldn't be used for detailed samples. Thank you for your support @trahay @ManuelSelva
But i still can't figure out the difference between "MEM_TRANS_RETIRED" and "MEM_UOPS_RETIRED". What's more , the doc didn't mention whether the CPU support PEBS or not...