caliper.1 (2010 09)

c
caliper(1)
Integrity Systems
caliper(1)
(Requires Optional HP Caliper Software)
The complex options are:
--process=[some:][OPT1,...]PATTERN
Each --process=some:
... argument provided to Caliper is interpreted as an additional filter.
Those filters are applied in order to each new process. If a filter matches the process, the behavior
(
measure, track, ignore) associated with the process is memorized. Caliper will use the
behavior of the last matching filter to determine what to do with the process.
When no OPT1
,... component is provided, the default interpretation is as follows: the PATTERN
component is interpreted as a list of
glob
patterns separated by colons (:); if the basename of the
executable matches any of those patterns, the process is measured, otherwise it is tracked.
The presence of keywords in OPT1
,... modifies those semantics as follow:
measure Processes matching this filter will be measured.
track Processes matching this filter will be tracked.
ignore Processes matching this filter will be ignored.
glob The PATTERN is interpreted as a list of colon-separated
glob patterns.
regexp The PATTERN is interpreted as a Python/Perl regular expression that is tested
using the
search() function (i.e., any non-empty match will be considered a posi-
tive match).
file The string used against the PATTERN is the basename of the main executable of
the process.
arg0argv0 The string used against the PATTERN is argument 0 of the process.
arg1argv1 The string used against the PATTERN is argument 1 of the process.
root The filter only matches the root process.
fork The filter only matches processes created via fork().
exec The filter only matches processes created by exec().
For keyword families
measure|track|ignore, glob|regexp and file|arg0
|arg1, only
the last keyword used in each family is considered. For the keyword family
root|
fork|exec,
multiple keywords will be considered as specifying a logical OR operation between the keywords.
The prefix
some: is only necessary when no option is provided and the PATTERN could be mis-
taken for one of the simple options (
root, root-forks, all, default).
--process=custom:
FUNCTION
Allows you to specify a Python function to be used as a filter for processes.
System-Wide Measurements
Only PMU-based measurements are available in system-wide mode (across all CPUs in the system,
instead of selected processes).
Measurements involving dynamic instrumentation see Measurement Categories ) and
cstack are not
supported in system-wide mode. The measurement can occur at any privilege level; the default privilege
level for system-wide mode is all: user and kernel space.
By default, samples are attributed to both a process and a load module, whenever possible. Alternatively,
you can specify (via
--scope) that samples be attributed to processes only or neither processes nor load
modules. Both alternatives reduce the overhead of collecting and reporting performance data.
(Note that attribution settings to
--scope do not affect attribution to samples in the kernel.)
In
pmu_trace, addresses referring to user-space modules will not get resolved regardless of the sample
attribution requested.
HP Caliper cannot locate an executable or a shared library on HP-UX if it is invoked using a relative
path. In addition, at certain times, executables and shared libraries cannot be located even if they are
specified with complete paths. If this problem occurs, the result can be a large number of samples
reported as "unattributed". The workaround is to use the
--module-search-path option to specify a
list of directories where the executables and shared libraries are located.
Usage model:
16 Hewlett-Packard Company − 16 − HP-UX 11i Version 3: September 2010