Kernel Profiler Modes
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
You can run the kernel profiler in one of several modes. The following table shows the modes that the kernel profiler supports and the requirements of each mode.
| Kernel profiler mode | Description | Requirements |
|---|---|---|
Monte Carlo profiling |
Periodically samples the program counter for the CPU. For more information, see Monte Carlo Profiling. |
|
System call profiling |
Counts calls made to the application programming interface (API) for the OS. For more information, see System Call Profiling. |
A run-time image built with IMGPROFILER=1 and WINCEMAP=1. |
Instrumented kernel profiling |
Tracks the amount of time that the kernel requires to execute calls internal to the kernel. For more information, see Instrumented Kernel Profiling. |
A run-time image built with IMGPROFILER=1 and WINCEMAP=1. |
The run-time image supports the kernel profiler when the IMGPROFILER variable is set because the Config.bib and Common.bib files specify an appropriate response to the value of this variable. For more information about the conditional logic in the Config.bib and Common.bib files, see Configuring the Config.bib and Common.bib Files for IMGPROFILER.
Note Although run-time images that support the kernel profiler also support CELog event tracking, kernel profiling is not related to CELog event tracking and the Remote Kernel Tracker, a tool associated with CELog.
See Also
Concepts
Setting Up the Kernel Profiler
Understanding Kernel Profiler Output