feat(rocprofiler-sdk): add hip event tracing sample - #11476
Draft
meserve-amd wants to merge 2 commits into
Draft
Conversation
✅ All Policy Checks Passed
📖 Need help? See the Policy FAQ for details on every check and how to fix failures. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Adds an example that exercises HIP event tracing and kernel dispatch tracing.
The sample runs two scenarios. The first is a simple case where a wait is requested for stream 2 waiting on stream 1 and a wait event is produced. In the second case, the same wait is requested after stream 1's event is complete, resulting in no barrier and no wait event being traced.
The example uses both callback tracing and buffer tracing to show how they might be used. The callback tracing allows us to log the program flow directly and is most of the code. I attempted to add a lot of prose to the log to explain the scenarios as they were executing.
Technical Details
I recommend reading the README.md included in the PR
Sample Output
Perhaps the most useful part of the sample is its output, so:
Issue Tracking
JIRA ID: AIPROFSDK-869
Test Plan
Adds sample test that verifies that verifies the example runs successfully, but does not place a hard requirement on a wait event being produced as that can be affected by hardware. (The sample includes a recommendation to increase the spin kernel duration if this occurs).
Test Result
Works on Navi4 tester
Submission Checklist