Fixing Performance Issue with API Tracing V2
Records right now will report basic raw data, no pre-processing in API anymore, and it will be left to the tool to process data from the output of synchronous callbacks of the API tracing records output
Change-Id: I8e5845e49e1228cb2fb60ca188ee748745b6a1af
[ROCm/rocprofiler commit: 4a33787c01]
이 커밋은 다음에 포함됨:
@@ -1476,6 +1476,21 @@ typedef struct {
|
||||
uint64_t id;
|
||||
} rocprofiler_tracer_external_id_t;
|
||||
|
||||
typedef enum {
|
||||
/**
|
||||
* No phase, it is an activity record or asynchronous output data
|
||||
*/
|
||||
ROCPROFILER_PHASE_NONE = 0,
|
||||
/**
|
||||
* Enter phase for API calls
|
||||
*/
|
||||
ROCPROFILER_PHASE_ENTER = 1,
|
||||
/**
|
||||
* Exit phase for API calls
|
||||
*/
|
||||
ROCPROFILER_PHASE_EXIT = 2
|
||||
} rocprofiler_api_tracing_phase_t;
|
||||
|
||||
/**
|
||||
* Tracing record, this will represent all the information reported by the
|
||||
* tracer regarding APIs and their data that were traced and collected
|
||||
@@ -1530,6 +1545,10 @@ typedef struct {
|
||||
* Thread id
|
||||
*/
|
||||
rocprofiler_thread_id_t thread_id;
|
||||
/**
|
||||
* API Tracing phase (Enter/Exit/None(Activity Records/Asynchronous Output Records))
|
||||
*/
|
||||
rocprofiler_api_tracing_phase_t phase;
|
||||
} rocprofiler_record_tracer_t;
|
||||
|
||||
/**
|
||||
|
||||
새 이슈에서 참조
사용자 차단