Adding user profiling and native XRT profiling to VE2 build #8745
Conversation
This file contains 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
Signed-off-by: Jason Villarreal <jvillar@xilinx.com>
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.
Problem solved by the commit
The profiling plugins for tracing user level events and tracing native XRT APIs were not built for VE2 devices so they were not available.
Risks (if any) associated the changes in the commit
Low risk as this only builds the plugins, they still need to be enabled by the user on VE2.
What has been tested and how, request additional testing if necessary
Integration with other applications that use user-level events must be tested on VE2 after this is built.
Documentation impact (if any)
No documentation impact.