Download NightTrace Manual

Tracing the Kernel
-verbose
Display the raw trace records with data interpretation and maximal formatting, including logical CPU ID, PID, and elapsed
time for all trace points. Note that this option creates huge output files. See “ktrace -verbose Listing” on page 11-19 for an
example.
To collect raw trace data from a running kernel in a KernelTrace trace event file named
raw_klog, run ktrace with the invocation:
$ ktrace -output raw_klog
While ktrace is running, run the workload to be measured. Terminate ktrace by
sending it a <Ctrl> <c> or using the kill(1) command to send it a SIGINTR signal.
CAUTION
Do not call clock_settime() from your application. This system call can corrupt both the system interval timer and Time Base
Register which both NightTrace and KernelTrace use for trace
event timings.
The KernelTrace trace event files created with ktrace have unique magic numbers, and
can be identified with the file(1) command. For example:
$ file raw_klog
raw_klog:
KernelTrace trace event file
To run ktrace using the KernelTrace trace event file raw_klog as input:
$ ktrace -input raw_klog > summary_file
The preceding example analyzes the trace records saved in raw_klog and writes textual
time summaries of kernel activity to summary_file.
KernelTrace trace event files are not compatible with the NightTrace tool set. However,
these files may be converted to NightTrace trace-file format with the ntfilter tool. See
“Converting KernelTrace Trace Event Files with ntfilter” on page 11-21 for more
information.
For more information about kernel tracing see the PowerMAX OS Real-Time Guide.
Viewing KernelTrace Trace Event Files with ktrace
11
Once you have a ktrace KernelTrace trace event file, you can use ktrace to analyze
and display it. You can use options to modify the summary reports.
11-13