System Call Profiling (Windows CE 5.0)
System call profiling counts the number of calls made to functions in the OS API. System call profiling differs from Monte Carlo profiling because there is no sampling in system call profiling. System call profiling captures each system call entry to obtain a count of the number of times each function is called. For more information about Monte Carlo profiling, see Monte Carlo Profiling.
You can perform system call profiling with or without a buffer that holds information captured by the kernel profiler. For information about the benefits and disadvantages of buffered and unbuffered profiling, see Buffered and Unbuffered Profiling.
System call profiling is useful when Monte Carlo profiling reveals a large number of hits in the ObjectCall function in the kernel. When an application calls a function that is exported by a system service, the ObjectCall function in the kernel routes the call to the appropriate system service. System call profiling monitors this ObjectCall function. With system call profiling, you can discover which functions are called most often. To improve performance or reduce the number of times you call system functions, put the caller thread into kernel mode to reduce the overhead for the call. For more information, see Full-Kernel Mode.
Note The ObjectCall function only calls functions that are in the OS API. You cannot use system call profiling to track calls within an application.
System call profiling does not provide a count by handle of function calls that are handle-based. System profiling simply counts function calls.
See Also
Kernel Profiler Modes | Setting up the Kernel Profiler | Controlling the Kernel Profiler
Send Feedback on this topic to the authors