-
Notifications
You must be signed in to change notification settings - Fork 9
datadev/emulator: MSI-X/MSI/INTx IRQ cascade + virtual MSI domain #280
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
Open
ruck314
wants to merge
7
commits into
pre-release
Choose a base branch
from
msi-irq
base: pre-release
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
f6185f9
datadev/emulator: MSI-X/MSI/INTx IRQ cascade + virtual MSI domain
ruck314 23c84b3
datadev: abort probe if FPGA advertises multiple IRQ types
ruck314 643863f
datadev: abort probe if BAR0 size is not the expected 16 MB
ruck314 2c762ce
datadev: only reject oversized BAR0 so the emulator's smaller fallbac…
ruck314 50e6f3d
emulator: advertise a single IRQ type per emu_irq_mode
ruck314 74fb5c6
datadev/emulator: drop the single-IRQ-type rejection
ruck314 64640eb
datadev: drop unused DmaDevice.irqType / DMA_IRQ_* defines
ruck314 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
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.
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.
I'm not sure what the context for this check is. afaik our firmware images all have fixed BAR sizes of 16MB right now.
BAR size difference doesn't necessarily indicate a register map mismatch (please correct me if I'm wrong @ruck314). If BAR is bumped to 32MB, AxiVersion/AxiPcieCore/etc. will still have the same offsets, unless explicitly changed in fw. In fact, we can have register map differences even if the BAR size is the same.
I also really dislike exceptions added for the sake of automated tests, especially considering this actually misses a case where BAR0 was 1MB back in 2017 with a different register map. Though, I'm pretty sure the driver has handling for these old firmware versions. Just skimming the git history here.
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.
@JJL772 This relates to an odd dynamic in the FPGA firmware's IP core: selecting the MSI-X IRQ silently changes the BAR0 size from 16MB to 64MB without any notification. Both the existing datadev driver and firmware assume BAR0 is 16MB.
I would have preferred a
!=check instead of>, but the emulator allocates less than 16MB and I couldn't find a good way to make it allocate exactly 16MB.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.
Thanks for the clarification. we can keep this check then
Uh oh!
There was an error while loading. Please reload this page.
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.
As a side note: When I run the C1100 with MSI interrupt the frame rate frequency for the PRBS testing into the CPU is incredibly stable compared to the legacy interrupt (comparing the min/max values) and able to increase FW->CPU bandwidth from 111Gb/s to 113Gb/s
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.
Nice to see performance improvements like that!!