CUPTI User's Guide

More documents

Recommendations

Info

CUptiResult cuptiUnsubscribe (CUpti_SubscriberHandlesubscriber)Removes a callback subscriber so that no future callbacks will be issued to that subscriber.Note:Thread-safety: this function is thread safe.Parameters:subscriber Handle to the initialize subscriberReturn values:CUPTI_SUCCESS on successCUPTI_ERROR_NOT_INITIALIZED if unable to initialized CUPTICUPTI_ERROR_INVALID_PARAMETER if subscriber is NULL or notinitializedCUDA Tools SDK CUPTI User’s Guide DA-05679-001_v01 | 70
CUpti_CallbackData Type ReferenceData passed into a runtime or driver API callback function.Data Fields◮ CUpti_ApiCallbackSite callbackSite◮ CUcontext context◮ uint32_t contextUid◮ uint64_t ∗ correlationData◮ uint32_t correlationId◮ const char ∗ functionName◮ const void ∗ functionParams◮ void ∗ functionReturnValue◮ const char ∗ symbolNameDetailed DescriptionData passed into a runtime or driver API callback function as the cbdata argument toCUpti_CallbackFunc. The cbdata will be this type for domain equal toCUPTI_CB_DOMAIN_DRIVER_API or CUPTI_CB_DOMAIN_RUNTIME_API.The callback data is valid only within the invocation of the callback function that is passedthe data. If you need to retain some data for use outside of the callback, you must make acopy of that data. For example, if you make a shallow copy of CUpti_CallbackData withina callback, you cannot dereference functionParams outside of that callback to access thefunction parameters. functionName is an exception: the string pointed to byfunctionName is a global constant and so may be accessed outside of the callback.Field DocumentationCUpti_ApiCallbackSite CUpti_CallbackData::callbackSitePoint in the runtime or driver function from where the callback was issued.CUcontext CUpti_CallbackData::contextDriver context current to the thread, or null if no context is current. This value can changefrom the entry to exit callback of a runtime API function if the runtime initializes aCUDA Tools SDK CUPTI User’s Guide DA-05679-001_v01 | 71
Page 1 and 2:
CUDA Tools SDKCUPTI User’s GuideD
Page 3 and 4:
CUPTIThe CUDA Profiling Tools Inter
Page 5 and 6:
CUPTI_CBID_RESOURCE_CONTEXT_CREATED
Page 7 and 8:
twice each time any of the CUDA run
Page 9 and 10:
device-specific limits. At any give
Page 11 and 12:
Sampling EventsThe event API can al
Page 13:
CapabilityEvent Name Description Ty
Page 16 and 17:
Page 18 and 19:
Page 20: CapabilityEvent Name Description Ty
Page 26 and 27: CUPTI ReferenceCUPTI VersionDefines
Page 28 and 29: CUPTI Result CodesEnumerations◮ e
Page 30 and 31: CUPTI_ERROR_INVALID_METRIC_IDCUPTI_
Page 32 and 33: CUPTI_ACTIVITY_COMPUTE_API_OPENCL =
Page 34 and 35: size_t ∗validBufferSizeBytes)Quer
Page 36 and 37: CUPTI_ACTIVITY_MEMCPY_KIND_HTOAcopy
Page 38 and 39: CUptiResult cuptiActivityEnqueueBuf
Page 40 and 41: CUptiResult cuptiActivityGetNumDrop
Page 42 and 43: CUpti_Activity Type ReferenceThe ba
Page 44 and 45: CUpti_ActivityKind CUpti_ActivityAP
Page 46 and 47: Detailed DescriptionThis activity r
Page 48 and 49: uint32_t CUpti_ActivityDevice::maxI
Page 50 and 51: uint64_t CUpti_ActivityEvent::value
Page 52 and 53: Field Documentationint32_t CUpti_Ac
Page 54 and 55: uint16_t CUpti_ActivityKernel::regi
Page 56 and 57: uint8_t CUpti_ActivityMemcpy::copyK
Page 58 and 59: CUpti_ActivityMemset Type Reference
Page 60 and 61: CUpti_ActivityMetric Type Reference
Page 62 and 63: CUPTI Callback APIData Structures
Page 64 and 65: Enable or disabled all callbacks fo
Page 66 and 67: Enumerator:CUPTI_CBID_RESOURCE_INVA
Page 68 and 69: Parameters:enable New enable state
Page 72 and 73: context.uint32_t CUpti_CallbackData
Page 74 and 75: CUpti_ResourceData Type ReferenceDa
Page 76 and 77: CUPTI Event APIData Structures◮ s
Page 78 and 79: CUPTI_EVENT_GROUP_ATTR_NUM_EVENTS =
Page 80 and 81: ∗eventValueBuffer, size_t ∗even
Page 82 and 83: CUPTI_DEVICE_ATTR_MAX_EVENT_DOMAIN_
Page 84 and 85: CUPTI_EVENT_GROUP_ATTR_PROFILE_ALL_
Page 86 and 87: valueSize The size of the value buf
Page 88 and 89: Return values:CUPTI_SUCCESSCUPTI_ER
Page 90 and 91: Parameters:device The CUDA deviceev
Page 92 and 93: Parameters:eventGroup The event gro
Page 94 and 95: flags Flags controlling the reading
Page 96 and 97: Return values:CUPTI_SUCCESSCUPTI_ER
Page 98 and 99: CUPTI_ERROR_INVALID_OPERATION if an
Page 100 and 101: CUPTI_METRIC_VALUE_KIND_PERCENT = 2
Page 102 and 103: enum CUpti_MetricCategoryEach metri
Page 104 and 105: metricArray Returns the IDs of the
Page 106 and 107: CUPTI_ERROR_NOT_INITIALIZEDCUPTI_ER
Page 108 and 109: CUPTI_ERROR_INVALID_PARAMETER if me
show all

CUPTI User's Guide

Create successful ePaper yourself

Delete template?

Save as template?