You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When looking at the Timestamp Operations in roctracer.h, I noticed there is no way to change the clock that roctracer uses to set timestamps. This forces the user to use a system clock, which is not guaranteed to be monotonic. It would be useful to have a rocm version of cuptiActivityRegisterTimestampCallback so that we can set the timestamps to be monotonic.
Thank you.
Operating System
CentOS Stream 9
GPU
N/A
ROCm Component
roctracer
The text was updated successfully, but these errors were encountered:
There are inherent underlying problems here which block this for being easily implemented. Roctracer/rocprofiler-sdk do not have control over the clock for GPU timestamps and those timestamps are given to us asynchronously. Thus, your callback cannot be invoked when the timestamp is recorded. It may be possible but it will likely require changes in the driver.
Side note, internally within the profiling tool libraries, we use CLOCK_BOOTTIME which is monotonic and generally aligns with the GPU timestamps (occasionally, we’ve detected skews which requires small shifts)
Suggestion Description
When looking at the Timestamp Operations in roctracer.h, I noticed there is no way to change the clock that roctracer uses to set timestamps. This forces the user to use a system clock, which is not guaranteed to be monotonic. It would be useful to have a rocm version of cuptiActivityRegisterTimestampCallback so that we can set the timestamps to be monotonic.
Thank you.
Operating System
CentOS Stream 9
GPU
N/A
ROCm Component
roctracer
The text was updated successfully, but these errors were encountered: