HP-UX Reference (11i v2 07/12) - 1 User Commands A-M (vol 1)

c
caliper(1)
For Integrity Systems Only
caliper(1)
Caliper 4.3 Caliper 4.3
(Requires Optional HP Caliper Software)
unwind while collecting call stack samples. The default depth is 32.
--metrics= EVENT_SET[:all|:user|:kernel
][,EVENT_SET]...
--metrics= CPU_EVENT[:EVENT_PARAM]...[
,CPU_EVENT]...
(Can also be specified with the
-m option.)
Specifies the event set or CPU events to measure. If no event is specified (or
--metrics= is
specified), then no metrics will be reported. (Note: Specifying
--metrics= is not valid for the cpu
and ecount measurements.)
EVENT_SET is a predefined collection of CPU events you specify only with the measurement,
cpu.
(See CPU Metrics EVENT_SET Description below for more information.)
CPU_EVENT is a CPU event as recorded by the Performance Monitoring Unit (PMU) of the proces-
sor. You can change the default CPU events recorded for any of the following measurements:
alat,
branch, cycles, dcache, dtlb,
ecount, fprof, icache, itlb, pmu_trac, traps.
You can list CPU events available (along with descriptions) by using
caliper info (see Informa-
tion Options below). Defaults specific to a given measurement can be found in the measurement’s
configuration file.
EVENT_PARAM allows you to change the privilege level (default:
user) and threshold (default: 0)
used when counting events. See
--event-defaults
above for the syntax of EVENT_PARAM.
--module-default=all
|none
Specifies the default setting for load module inclusion in the measurement.
--module-exclude=
MODULE[:MODULE]...
Specifies the load modules to be excluded from measurement. Module names can be given as a simple
file name (
libapplib1.so
) which matches libraries of this name in any directory; a full-path file
name (
/home/dev/libs/libapplib1.so
) which matches only this one specific library; or a
full-path directory name (
/usr/lib/) which matches all libraries within this directory or any lower
sub-directories.
Note that the trailing / is required to distinguish a directory name.
For instrumentation-based measurements (
acount, cgprof, fcount, fcover), the specified load
modules are not instrumented; for all other measurements, any samples in the specified load modules
are simply discarded.
--module-include=
MODULE[:MODULE]...
Specifies the load modules to be included in the measurement. Module names can be given as a sim-
ple file name (
libapplib1.so
) which matches libraries of this name in any directory; a full-path
file name (
/home/dev/libs/libapplib1.so
) which matches only this one specific library; or a
full-path directory name (
/usr/lib/) which matches all libraries within this directory or any lower
sub-directories.
Note that the trailing / is required to distinguish a directory name.
--module-search-path=
DIRECTORY[:DIRECTORY]...
Specifies a list of directories to be searched when a load module file (executable or shared library) can-
not be found. A load module may not be found if the measured process uses chroot(2) or chdir(2) and
then loads libraries or executes other binaries using relative paths. (See also the entry for this option
in the section, Reporting Options.)
--process= {default|all|root|root-forks|[some:][OPT,...]PATTERN[, PATTERN]...}
(Can also be specified with the
-p option).
Specifies which processes in an application’s process tree should be measured.
Use root to measure only your application’s root process.
Use root-forks to measure your application’s root process and any processes it forks.
Use all (the default) to measure all your application’s processes.
For more information, see Process Selection below.
--sampling-spec=TIME_PERIOD
--sampling-spec=EVT_PERIOD[,VARIATION [,CPU_EVENT[:EVENT_PARAM]...]]
96 Hewlett-Packard Company − 6 − HP-UX 11i Version 2: December 2007 Update