The following are known issues with the current release.

• The Continuous event collection mode CUPTI_EVENT_COLLECTION_MODE_CONTINUOUS is supported only on Tesla devices.
• Profiling results might be inconsistent when auto boost is enabled. Profiler tries to disable auto boost by default. But it might fail to do so in some conditions and profiling will continue and results will be inconsistent. API cuptiGetAutoBoostState() can be used to query the auto boost state of the device. This API returns error CUPTI_ERROR_NOT_SUPPORTED on devices that don't support auto boost. Note that auto boost is supported only on certain Tesla devices with compute capability 3.0 and higher.
• CUPTI doesn't populate the activity structures which are deprecated, instead the newer version of the activity structure is fill with the information.
• While collecting events in continuous mode, event reporting may be delayed i.e. event values may be returned by a later call to readEvent(s) API and the event values for the last readEvent(s) API may get lost.