PAPI RAPL for Xeon Phi MIC

[flyingbear]

Hi
Does RAPL supported on Xeon Phi?
I am trying to use RAPL on Xeon Phi in native mode.
I installed PAPI with command
./configure --prefix=$PWD/../mic-native-build/ --with-components=rapl --with-mic to config the native mode.
After make and make install, I scp the mic-native-build folder to mic0, and then ssh to mic0 and run the command papi_component_avail.
It shows that "Name: rapl Linux SandyBridge RAPL energy measurements. Disabled: CPU family not supported."
Is there any other way to configure the RAPL for native mode? What is wrong with my configuration?

[root@hydra-mic0 bin]# ./papi_component_avail
Available components and hardware information.
--------------------------------------------------------------------------------
PAPI Version : 5.3.0.0
Vendor string and code : GenuineIntel (1)
Model string and code : 0b/01 (1)
CPU Revision : 2.000000
CPUID Info : Family: 11 Model: 1 Stepping: 2
CPU Max Megahertz : 1100
CPU Min Megahertz : 600
Hdw Threads per core : 4
Cores per Socket : 57
Sockets : 1
CPUs per Node : 228
Total CPUs : 228
Running in a VM : no
Number Hardware Counters : 2
Max Multiplex Counters : 64
--------------------------------------------------------------------------------

Compiled-in components:
Name: perf_event Linux perf_event CPU counters
Name: perf_event_uncore Linux perf_event CPU uncore and northbridge
\-> Disabled: No uncore PMUs or events found
Name: rapl Linux SandyBridge RAPL energy measurements
\-> Disabled: CPU family not supported

Active components:
Name: perf_event Linux perf_event CPU counters
Native: 139, Preset: 14, Counters: 2


--------------------------------------------------------------------------------
component.c PASSED

[jagode00]

In order to measure power usage and energy consumption on the MIC card, you will have to use PAPI's MIC component instead of the RAPL component.
In fact, PAPI offers two components to do this:
First component is called “micpower” – and it runs in native mode. Meaning both, the actual application as well as PAPI are running natively on the coprocessor and its OS, without being offloaded from a host system.
The second component is called “host_micpower” and this one is much more convenient for users. In this case, PAPI is offloaded from the host, and only the application is running on the MIC card. The power data is exported through an interface - the MicAccessAPI - that’s distributed with the Intel Manycore Platform Software Stack.

Both MIC components offer a README file with more details.

Thanks,
Heike.

[James Ralph]

RAPL does not support the MICs, but you could try the micpower component.

[flyingbear]

Hi Heike and James
Thanks for the kindly replying.
Since my application is running in native mode, I am trying the micpower component.
Here is my config command.

./configure --prefix=$(PATH_TO_mic-native-build) --with-mic --with-components=micpower
After install succesfully and scp the install folder to mic0, i run command ./papi_native_avail in bin folder and get following.

===============================================================================
Native Events in Component: micpower
===============================================================================
| micpower:::tot0 |
| Total power, win 0 |
--------------------------------------------------------------------------------
| micpower:::tot1 |
| Total power, win 1 |
--------------------------------------------------------------------------------
| micpower:::pcie |
| PCI-E connector power |
--------------------------------------------------------------------------------
| micpower:::inst |
| Instantaneous power |
--------------------------------------------------------------------------------
| micpower:::imax |
| Max Instantaneous power |
--------------------------------------------------------------------------------
| micpower:::c2x3 |
| 2x3 connector power |
--------------------------------------------------------------------------------
| micpower:::c2x4 |
| 2x4 connector power |
--------------------------------------------------------------------------------

I change the micpower_basic example in papi-5.3.0/src/components/micpower/tests folder, I want to test the total energy consumption of the kernel.
Here is my code in attatchment with micpower_main.c.
icc -I$(PATH_to_mic-native-build)/include -mmic micpower_main.c -c
icc -mmic micpower_main.o -o main.x $(PATH_to_mic-native-build)/lib/libpapi.a
Here is the output of main.x
[root@hydra-mic0 ~]# ls
main.x mic-native-build micpower_basic mklCTest.x saves seidel.x temp
[root@hydra-mic0 ~]# ./main.x
n=500
CID NAME: 0 perf_event
CID NAME: 1 perf_event_uncore
CID NAME: 2 micpower
mic_cid=2
0.098000 0.097000 0.099000 0.177000 0.027000 0.029000 0.043000 0.021000 0.000000 0.000998 0.029000 0.000000 0.001000 0.035000 0.000000 0.001501

I can adjust the problem size throught N in micpower.c,
The thing is that the micpower:::tot0 and micpower:::tot1 nearly no change at all no matter I give N=500 or N=200 or N=1000 or just comment the kernel.
I can not understand the power number output by micpower here.
Do you have any explanation on these numbers?