mem-cache: findBlock shouldn't assume blk can always be found #168
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
- CDP uses findBlock to get content of cache block, and CDP is speculative: CDP is placed in L2 and can be notified by L1 hits. But GEM5 employs **mostly**-inclusive cache, where an L1 hit does not guarantees L2 hit. So a CDP notification might misses in L2. - To avoid segmentation fault when blk is not found, we always check whether blk is null Change-Id: Ic0b20109ea42621cbf74c184daa00b0633123384
tastynoob
approved these changes
Aug 28, 2024
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.
Change-Id: Ic0b20109ea42621cbf74c184daa00b0633123384