dcpicat - Prints the contents of a profile file.
dcpicat profile files
Dcpicat reads one or more profile files generated by
dcpid(1), and dumps their contents in ASCII to standard output. The
output of dcpicat will mostly be useful to people debugging DCPI, or to
people who want the raw profile data as input to new analysis tools. Users
will get more meaningful output from other analysis tools such as
dcpiprof(1), dcpilist(1) and
INTERPRETING THE OUTPUT
For each profile file, dcpicat first prints a header that
describes the profile, and then prints the sample counts associated with
each program-counter value. The following sample output from dcpicat
is used to explain the output format:
event 470352 cycles:63488:10000
event 134705 imiss:4096:10000
0x00012006cbb8 29 27
0x00012006cbd0 10 0
0x00012006cbd4 1 0
0x00012006cbd8 2 0
0x00012006cbe0 3 2
0x00012006cbe8 2 0
The various fields in the header should be interpreted as follows:
- This is a profile for xemacs.
- The image identifier for xemacs. The first fourteen digits indicate
the UTC time at which the image was created. (The format of the time is
yyyymmddhhmmss.) The last six digits of this number should match
the last six digits of dcpiscan's output for this image.
- The label assigned to this profile. (This field is optional.)
- A path where the image is likely to be found.
- The name of the epoch during which the profile was
- The name of the machine on which the
profile was collected.
- The hexadecimal byte-size of the text section of the image.
- One such line is present for each event type present in the profile. The example profile given above contains two events: cycles, and imiss. Each event entry has the form "W X:Y:Z". The "W" portion is the sum of this event's count across all pc values recorded in this profile. "X" is the event name. "Y" is the sampling period used to sample this event: i.e., one such event occurrence is recorded every "Y" occurrences of the event. "Z" is 10000 times the fraction of the time the event was being monitored. (When multiple events are being multiplexed onto the same hardware counter, "Z" will be less than 10000.)
After the header, the multi-column output lists event counts per pc. If
there are "n" events recorded in the profile, there will be "n+1" columns.
The first column is the pc value in increasing address order. Skipped pc
values have zero counts for all events.
The remaining columns contain the count per event type. The columns are in
the same order as the "event" lines in the profile header. For the example
given above, the second column contains cycle counts and the third column
contains imiss counts. For example, the pc value "0x00012006cbb8" has
accumulated "29" cycle samples and "27" imiss samples.
For more information, see the DCPI project home page
Hewlett-Packard Company. All rights reserved.