Skip to content
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

[XDP] Bug fixes to parsing of graph-based xrt.ini settings #8722

Merged
merged 2 commits into from
Jan 28, 2025

Conversation

pgschuey
Copy link
Collaborator

Problem solved by the commit

Parsing of some profile/trace settings was not correct

Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered

A few bugs were found regarding parsing of graph names

How problem was solved, alternative solutions (if any) and why they were rejected

Subgraph support fixed for interface tiles, memory modules, and kernel = all

Risks (if any) associated the changes in the commit

Known issue: support is constrained by metadata. This needs to be updated to better support graphs/subgraphs, core- and DMA-only tiles, etc.

What has been tested and how, request additional testing if necessary

Tested on vck190 and vek280

Documentation impact (if any)

When specifying subgraphs and kernel=all, users will get what they ask for, plus possibly more.

Paul Schumacher added 2 commits January 27, 2025 17:06
Signed-off-by: Paul Schumacher <[email protected]>
Signed-off-by: Paul Schumacher <[email protected]>
@pgschuey pgschuey requested a review from jvillarre as a code owner January 28, 2025 19:06
@pgschuey pgschuey changed the title Parsing fixes [XDP] Bug fixes to parsing of graph-based xrt.ini settings Jan 28, 2025
@pgschuey pgschuey requested review from vipangul and removed request for jvillarre January 28, 2025 19:07
@jvillarre jvillarre merged commit 337b125 into Xilinx:master Jan 28, 2025
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants