Share via


ProfilerHitEx (Windows CE 5.0)

Send Feedback

This function is implemented in the kernel, and is called by profiler ISR to record a profiling sample.

VOID ProfilerHitEx(  OEMProfilerData* pData);

Parameters

  • pData
    [in] Pointer to an OEMProfilerData structure containing hardware-specific profiling data.

Return Values

None.

Remarks

In the case of buffered and unbuffered profiler operation, ProfilerHitEx ignores all contents of pData except the return address.

In the case of CeLog profiling, ProfilerHitEx sends the contents of pData to the Celog data stream. For more information, see Celog.lib and Remote Kernel Tracker and CeLog Event Tracking.

If the profiler ISR is generating interrupts with a timer, its calls to ProfilerHitEx result in standard Monte Carlo profiling functionality, where samples are gathered at regular time intervals. For more information, see Monte Carlo Profiling.

If the profiler ISR is generating interrupts on rollover events for various performance counters, its calls to ProfilerHitEx result in more general functionality, where samples are gathered at regular intervals of those performance counters.

For example, if the OEM's custom profiler is generating interrupts after a specified number of instruction cache misses, the profiler report highlights the functions that generated the largest number of instruction cache misses rather than the functions that consumed the largest amount of processor time.

You can use ProfilerHitEx to expose custom profiling data for their BSP.

Requirements

OS Versions: Windows CE 5.0 and later.
Header: Profiler.h.
Link Library: Coredll.lib.

See Also

OEMProfilerData | ProfilerHit | ProfileStartEx

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.