HP XC System 3.x Software - Manual (Page 61)

:
:
If you run the same hpcpiprof command and specify the label name (hpcpiprof -label
myLabel
), hpcpiprof displays event counts for code executed in all images for myApp, such
as code in shared libraries called from myApp. An extract of the output is as follows:
% hpcpiprof -label myLabel
Event Name Events Period Samples
---------- ------------- ------ --------
CPU_CYCLES 3914574240000 60000 65242904
CPU_CYCLES % cum% image
---------- ----- ------ --------------------------
198708e7 50.8% 50.8% libm-2.3.4.so
192510e7 49.2% 99.9% myApp
192e7 0.0% 100.0% vmlinux-2.6.9-34.7hp.XCsmp
:
:
Using the label shows that of the CPU cycles used for myApp, the majority of the CPU cycles
were used in the libm-2.3.4.so library. To display which procedures in the libm-2.3.4.so
library were used by myApp and the number of CPU cycles used in each procedure, enter the
following command:
% hpcpiprof -label myLabel libm-2.3.4.so
The output is as follows:
libm-2.3.4.so: not found.
+ Found and using /lib/tls/libm-2.3.4.so
-------
Event Name Events Period Samples
---------- ------------- ------ --------
CPU_CYCLES 1987076640000 60000 33117944
CPU_CYCLES % cum% procedure image
---------- ----- ------ --------------- -------------
100456e7 50.6% 50.6% __ieee754_sqrtf libm-2.3.4.so
98252e7 49.4% 100.0% __logf libm-2.3.4.so
The hpcpiprof utility prints the statement libm-2.3.4.so: not found because it first
searches for the libm-2.3.4.so image in the current working directory and fails. It finds and
uses the libm-2.3.4.so image in the path /lib/tls/libm-2.3.4.so, as indicated in the
subsequent statement.
For descriptions of the output data, see “Viewing Per-Procedure Data: hpcpiprof image_name”
(page 46) .
Step 5: Stopping the HPCPI Daemon
When you are done collecting data, enter the following command to stop the HPCPI daemon:
% hpcpictl quit
Simple HPCPI Session Using Labels 61