caliper.1 (2010 09)

c
caliper(1)
Integrity Systems
caliper(1)
(Requires Optional HP Caliper Software)
--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_trace, 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 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.
For instrumentation-based measurements (
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)
cannot 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 .)
--omr=OPCODE_MATCH_CHANNEL,MIFB,OPCODE_MATCH
,OPCODE_MASK[,PROC_FLAGS]
Specifies the bits to program the PMU’s opcode matching registers. Forces PMU event monitoring to
be constrained based on Itanium processor encoding (opcode) of an instruction.
OPCODE_MATCH_CHANNEL is 0 or 1, where:
0 Corresponds to PMC 8 on Itanium, PMC 32 and 33 on Dual-Core Itanium and Quad-Core pro-
cessors.
1 Corresponds to PMC 9 on Itanium, PMC 34 and 35 on Dual-Core Itanium and Quad-Core pro-
cessors.
MFIB is a combination of characters to specify match slot instructions:
m Match M-slot
i Match I-slot
f Match F-slot
HP-UX 11i Version 3: September 2010 − 7 − Hewlett-Packard Company 7