[XRT-SMI] Add new report for context health data capture for npu3 #9418
Conversation
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
Signed-off-by: Akshay Tondak <[email protected]>
aktondak
requested review from
AShivangi,
chvamshi-xilinx and
rozumx
as code owners
AShivangi
approved these changes
Nov 7, 2025
aktondak
changed the title
Contributor
|
clang-tidy review says "All clean, LGTM! 👍" |
Contributor
|
clang-tidy review says "All clean, LGTM! 👍" |
kashif
pushed a commit
to kashif/XRT
that referenced
this pull request
Nov 22, 2025
Signed-off-by: Akshay Tondak <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
This PR adds a new report for capturing context health on npu3
Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered
https://jira.xilinx.com/browse/AIESW-16877
How problem was solved, alternative solutions (if any) and why they were rejected
Solved using runtime check for hardware type and creating correct report generator based on it. Further each report generator generates strx/npu3 specific reports.
Risks (if any) associated the changes in the commit
None
What has been tested and how, request additional testing if necessary
Not tested yet. Blocked by driver side plumbing for providing aie4/npu3 context health data
Documentation impact (if any)
None