11.07.2015 Views

CUPTI User's Guide

CUPTI User's Guide

CUPTI User's Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

typedef uint32_t CUpti_CallbackIdAn ID for a driver API, runtime API, resource or synchronization callback. Within adriver API callback this should be interpreted as a CUpti_driver_api_trace_cbid value.Within a runtime API callback this should be interpreted as aCUpti_runtime_api_trace_cbid value. Within a resource API callback this should beinterpreted as a CUpti_CallbackIdResource value. Within a synchronize API callback thisshould be interpreted as a CUpti_CallbackIdSync value.Enumeration Type Documentationenum CUpti_ApiCallbackSiteSpecifies the point in an API call that a callback is issued. This value is communicated tothe callback function via CUpti_CallbackData::callbackSite.Enumerator:<strong>CUPTI</strong>_API_ENTER<strong>CUPTI</strong>_API_EXITenum CUpti_CallbackDomainThe callback is at the entry of the API call.The callback is at the exit of the API call.Callback domains. Each domain represents callback points for a group of related APIfunctions or CUDA driver activity.Enumerator:<strong>CUPTI</strong>_CB_DOMAIN_INVALID<strong>CUPTI</strong>_CB_DOMAIN_DRIVER_APIdriver API functions.<strong>CUPTI</strong>_CB_DOMAIN_RUNTIME_APIall runtime API functions.<strong>CUPTI</strong>_CB_DOMAIN_RESOURCECUDA resource tracking.<strong>CUPTI</strong>_CB_DOMAIN_SYNCHRONIZECUDA synchronization.enum CUpti_CallbackIdResourceInvalid domain.Domain containing callback points for allDomain containing callback points forDomain containing callback points forDomain containing callback points forCallback IDs for resource domain, <strong>CUPTI</strong>_CB_DOMAIN_RESOURCE. This value iscommunicated to the callback function via the cbid parameter.CUDA Tools SDK <strong>CUPTI</strong> User’s <strong>Guide</strong> DA-05679-001_v01 | 65

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!