-
Notifications
You must be signed in to change notification settings - Fork 18
Added stream_id to Perfetto annotations #274
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
base: amd-staging
Are you sure you want to change the base?
Conversation
I see the stream_id for the
|
I just merged with |
Based on the `ROCPROFSYS_ROCM_GROUP_BY_QUEUE` setting, group these traces accordingly in the Perfetto trace. Signed-off-by: David Galiffi <[email protected]>
…ption. If it is not supported, we cannot group by HIP stream and must default to grouping by HSA queue
Signed-off-by: David Galiffi <[email protected]>
ROCPROFILER_CALL(rocprofiler_configure_callback_tracing_service( | ||
_data->primary_ctx, ROCPROFILER_CALLBACK_TRACING_HIP_STREAM, nullptr, 0, | ||
tool_hip_stream_callback, nullptr)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rocprofiler_configure_callback_tracing_service
will return an error in this case if both "kernel-dispatch" and "memory-copy" are enabled.
Instead, you can change the logic to something like this:
if ROCPROFILER_BUFFER_TRACING_KERNEL_DISPATCH
setup specific to kernel-dispatch
if ROCPROFILER_BUFFER_TRACING_MEMORY_COPY
setup specific to memory-copy
if ROCPROFILER_BUFFER_TRACING_MEMORY_COPY or ROCPROFILER_BUFFER_TRACING_KERNEL_DISPATCH
rocprofiler_configure_callback_tracing_service(ROCPROFILER_CALLBACK_TRACING_HIP_STREAM)
Signed-off-by: David Galiffi <[email protected]>
… called only once
The HIP_STREAM callback was new in ROCPROFILER v0.7.0 Signed-off-by: David Galiffi <[email protected]>
Signed-off-by: David Galiffi <[email protected]>
rocprofiler-systems Pull Request
Related Issue
What type of PR is this? (check all that apply)
Technical Details
Have you added or updated tests to validate functionality?
Added / Updated documentation?
Have you updated CHANGELOG?