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.
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
[dv] Add spurious responses to memory agent #2185
[dv] Add spurious responses to memory agent #2185
Changes from all commits
ae13c5f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The
!spurious_response
bit seems slightly surprising here. Should the monitor really care about whether the response was the one we were waiting for? I guess the problem is theoutstanding_accesses
counter, but maybe that really belongs in the driver or the sequence rather than the monitor, since those components know whether they have anything "in flight".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.
This is partially down to laziness on my part but pre this change spurious responses didn't exist and downstream users of the monitor (i.e. those things connecting to the
item_collected_port
) were expecting everything they receive to represent an actual transaction that occurred (in particular the co-sim scoreboard). If we output spurious responses here we'll need all downstream users of the monitor to filter out spurious responses. This felt like a cleaner design.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.
Ok, that feels reasonable. Maybe an example of where "the principled solution" is also the wrong one :-)