HP Caliper 5.3 User Guide (5900-1558, February 2011)

For more information, see “Performing CPU Metrics Analysis ” (p. 151).
NOTE: This option was formerly known as --cpu-metrics-details. The former option name
is still accepted by HP Caliper, but will be removed in a future release.
--csv-file
--csv-file filename[append|create][,per-process|shared][,unique]
Generates report output in Comma Separated Values (CSV) format. You can produce a CSV report
for any HP Caliper measurement.
The CSV reports are formatted to load in an easy-to-read format in a spreadsheet using a fixed-width
typeface such as Courier or for further processing. The filename is the destination.
You can generate reports in CSV or text formats on any given run.
append Adds the report results to the end of an existing file that has the specified name.
create Creates a file with the specified name and writes the report results to the file.
Replaces any existing file with the specified name.
per-process For multiprocess reports, creates individual report files for each process with
program name appended to each file.
shared Creates a single file containing the results for all processes. This is the default.
unique Appends the process ID to the data file name.
Examples
To generate a CSV report:
caliper measurement --csv-file filename ...
To generate a CSV file from information previously saved in a data file:
$ caliper report --csv-file filename datafilename
--dcache-data-profile
Specifies that the dcache measurement should report a Data Summary. The Data Summary report
shows data cache samples aggregated to global variables and process regions such as stack,
heap, data, and so forth.
This option is used only with the dcache measurement. By default, dcache does not report a data
summary. This option was formerly known as --data-summary. The former option name is still
accepted by HP Caliper, but is deprecated and will be removed in a future release.
For more information, see “dcache Measurement Report Description” (page 186).
--database
See “-d or --database” (p. 48).
--dbrp
--dbrp=DBRP_INDEX,PLM,ADDR_MATCH,ADDR_MASK,PROC_FLAGS
Specifies the bits to program the PMU's data address range matching registers. Forces event
monitoring to be constrained by data address ranges.
DBRP_INDEXX can be 0, 1, 2 or 3. It identifies one of the four Data Breakpoint Registers (DBRs)
used to specify the desired address range.
PLM specifies the privilege level setting. The privilege levels available are: "user",
"kernel", and "all".
--csv-file 57