-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIRIUS timers and roctrace
#961
Comments
Instead of tracing the whole application or test, a smaller session can be traced as shown in Tracing Control for API or Code Block sesion of ROCm Docs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Working using PR #940 and more specifically,
roctrace
, I found out that the timers logged by SIRIUS itself can be used asregions
in Perfetto, as shown below:However, the
rocprof
post-processing script crashesThat's because 3 timers are outside of the scope of
rocprof
:PROFILE_START("sirius")
linkPROFILE("sirius::initialize")
linkPROFILE_STOP("sirius")
linkOut of scope meaning that the log of
rocprof
only logs aSTOP
but the correspondingSTART
is missing.Quick solution to enable tracing was to comment-out the three above timer lines.
The text was updated successfully, but these errors were encountered: