Profiler Control

cudaError_t cudaProfilerInitialize (const char * configFile, const char * outputFile, cudaOutputMode_t outputMode)

Using this API user can initialize the CUDA profiler by specifying the configuration file, output file and output file format. This API is generally used to profile different set of counters by looping the kernel launch. The configFile parameter can be used to select profiling options including profiler counters. Refer to the 'Compute Command Line Profiler User Guide' for supported profiler options and counters.

Limitation: The CUDA profiler cannot be initialized with this API if another profiling tool is already active, as indicated by the cudaErrorProfilerDisabled return code.

Typical usage of the profiling APIs is as follows:

for each set of counters/options
{
cudaProfilerInitialize(); //Initialize profiling,set the counters/options in the config file
...
cudaProfilerStart();
// code to be profiled
cudaProfilerStop();
...
cudaProfilerStart();
// code to be profiled
cudaProfilerStop();
...
}

Parameters:

Returns:

Note:

See also:

cudaError_t cudaProfilerStart (void)

Enables profile collection by the active profiling tool for the current context. If profiling is already enabled, then cudaProfilerStart() has no effect.

cudaProfilerStart and cudaProfilerStop APIs are used to programmatically control the profiling granularity by allowing profiling to be done only on selective pieces of code.

Returns:

Note:

See also:

cudaError_t cudaProfilerStop (void)

Disables profile collection by the active profiling tool for the current context. If profiling is already disabled, then cudaProfilerStop() has no effect.

cudaProfilerStart and cudaProfilerStop APIs are used to programmatically control the profiling granularity by allowing profiling to be done only on selective pieces of code.

Returns:

Note:

See also: