Software Tuning, Performance Optimization & Platform Monitoring
Discussion regarding monitoring and software tuning methodologies, Performance Monitoring Unit (PMU) of Intel microprocessors, and platform updating.

[PCM] pcm-power.x tool does not report the frequency bins.

Thomas_W_Intel
Employee
262 Views

hilgeman commented on the Intel PCM article:

The pcm-power.x tool does not report the frequency bins. No matter what bins I use with the -p 0 option and -a/-b/-c frequency values, the percentages always remain zero:

[root@PowerEdgeR630-BM4GS42 IntelPerformanceCounterMonitorV2.8]# ./pcm-power.x -p 0 -m -1 -- /bin/sleep 5

 Intel(r) Performance Counter Monitor V2.8 (2014-12-18 12:52:39 +0100 ID=ba39a89)

 Power Monitoring Utility
 Copyright (c) 2011-2014 Intel Corporation
Number of physical cores: 24
Number of logical cores: 24
Number of online logical cores: 24
Threads (logical cores) per physical core: 1
Num sockets: 2
Physical cores per socket: 12
Core PMU (perfmon) version: 3
Number of core PMU generic (programmable) counters: 8
Width of generic (programmable) counters: 48 bits
Number of core PMU fixed counters: 3
Width of fixed counters: 48 bits
Nominal core frequency: 2500000000 Hz
Package thermal spec power: 120 Watt; Package minimum power: 61 Watt; Package maximum power: 240 Watt;
Socket 0: 2 memory controllers detected with total number of 4 channels. 2 QPI ports detected.
Socket 1: 2 memory controllers detected with total number of 4 channels. 2 QPI ports detected.



MC counter group: -1
PCU counter group: 0
Freq bands [0/1/2]: 1200 MHz; 2000 MHz; 4000 MHz;
Update every -1.00 seconds

Executing "/bin/sleep" command:
DEBUG: caught signal to interrupt (Child exited).
Program /bin/sleep launched with PID: 61193
Program exited with status 0
----------------------------------------------------------------------------------------------
Time elapsed: 6001 ms
Called sleep function for 1000 ms
S0P0; QPIClocks: 14404115546; L0p Tx Cycles: 0.00%; L1 Cycles: 0.00%
S0P1; QPIClocks: 14404115458; L0p Tx Cycles: 0.00%; L1 Cycles: 0.00%
S0; PCUClocks: 6001705505; Freq band 0/1/2 cycles: 0.00%; 0.00%; 0.00%
S0; Consumed energy units: 3290124; Consumed Joules: 200.81; Watts: 33.46; Thermal headroom below TjMax: 56
S0; Consumed DRAM energy units: 2028732; Consumed DRAM Joules: 31.04; DRAM Watts: 5.17
S1P0; QPIClocks: 14404127778; L0p Tx Cycles: 0.00%; L1 Cycles: 0.00%
S1P1; QPIClocks: 14404127814; L0p Tx Cycles: 0.00%; L1 Cycles: 0.00%
S1; PCUClocks: 6001733045; Freq band 0/1/2 cycles: 0.00%; 0.00%; 0.00%
S1; Consumed energy units: 3441496; Consumed Joules: 210.05; Watts: 35.00; Thermal headroom below TjMax: 53
S1; Consumed DRAM energy units: 2003120; Consumed DRAM Joules: 30.65; DRAM Watts: 5.11
----------------------------------------------------------------------------------------------
Cleaning up
 Freeing up all RMIDs

regards,

-Martin

Martin,

I could reproduce this on an Intel Xeon E5 v3 processor, and we are looking into right now.

Kind regards

Thomas

0 Kudos
0 Replies
Reply