CUPTI User's Guide

More documents

Recommendations

Info

enum CUpti_MetricCategoryEach metric is assigned to a category that represents the general type of the metric. Ametric’s category is accessed using cuptiMetricGetAttribute and theCUPTI_METRIC_ATTR_CATEGORY attribute.Enumerator:CUPTI_METRIC_CATEGORY_MEMORYCUPTI_METRIC_CATEGORY_INSTRUCTIONCUPTI_METRIC_CATEGORY_MULTIPROCESSORmetric.CUPTI_METRIC_CATEGORY_CACHECUPTI_METRIC_CATEGORY_TEXTUREenum CUpti_MetricValueKindA memory related metric.An instruction related metric.A cache related metric.A multiprocessor relatedA texture related metric.Metric values can be one of several different kinds. Corresponding to each kind is amember of the CUpti_MetricValue union. The metric value returned bycuptiMetricGetValue should be accessed using the appropriate member of that unionbased on its value kind.Enumerator:CUPTI_METRIC_VALUE_KIND_DOUBLEThe metric value is a 64-bit double.CUPTI_METRIC_VALUE_KIND_UINT64The metric value is a 64-bit integer.CUPTI_METRIC_VALUE_KIND_PERCENT The metric value is a percentagerepresented by a 64-bit double. For example, 57.5% is represented by the value57.5.CUPTI_METRIC_VALUE_KIND_THROUGHPUT The metric value is athroughput represented by a 64-bit integer. The unit for throughput values isbytes/second.Function DocumentationCUptiResult cuptiDeviceEnumMetrics (CUdevice device, size_t ∗arraySizeBytes, CUpti_MetricID ∗ metricArray)Returns the metric IDs in metricArray for a device. The size of the metricArray buffer isgiven by ∗arraySizeBytes. The size of the metricArray buffer must be at leastnumMetrics ∗ sizeof(CUpti_MetricID) or else all metric IDs will not be returned. Thevalue returned in ∗arraySizeBytes contains the number of bytes returned in metricArray.CUDA Tools SDK CUPTI User’s Guide DA-05679-001_v01 | 102
Parameters:device The CUDA devicearraySizeBytes The size of metricArray in bytes, and returns the number of byteswritten to metricArraymetricArray Returns the IDs of the metrics for the deviceReturn values:CUPTI_SUCCESSCUPTI_ERROR_NOT_INITIALIZEDCUPTI_ERROR_INVALID_DEVICECUPTI_ERROR_INVALID_PARAMETER if arraySizeBytes or metricArray areNULLCUptiResult cuptiDeviceGetNumMetrics (CUdevice device, uint32_t∗ numMetrics)Returns the number of metrics available for a device.Parameters:device The CUDA devicenumMetrics Returns the number of metrics available for the deviceReturn values:CUPTI_SUCCESSCUPTI_ERROR_NOT_INITIALIZEDCUPTI_ERROR_INVALID_DEVICECUPTI_ERROR_INVALID_PARAMETER if numMetrics is NULLCUptiResult cuptiEnumMetrics (size_t ∗ arraySizeBytes,CUpti_MetricID ∗ metricArray)Returns the metric IDs in metricArray for all CUDA-capable devices. The size of themetricArray buffer is given by ∗arraySizeBytes. The size of the metricArray buffermust be at least numMetrics ∗ sizeof(CUpti_MetricID) or all metric IDs will not bereturned. The value returned in ∗arraySizeBytes contains the number of bytes returnedin metricArray.Parameters:arraySizeBytes The size of metricArray in bytes, and returns the number of byteswritten to metricArrayCUDA Tools SDK CUPTI User’s Guide DA-05679-001_v01 | 103
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:
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 70 and 71: CUptiResult cuptiUnsubscribe (CUpti
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 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

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

Delete template?

Save as template?