Fix uncached/cached access priority #915
Merged
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
give port A exclusive access
do not use lock feature for bus muxes
direct/uncached accesses cannot interrupt cache block operations
Accessing zero (= null pointer) is no good thing. Besides that, there is no need for a function to explicitly clear all active reservation sets
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.
With this PR the caches ensure that uncached accesses always have lower priority than cache block operation. Thus, cache block operations will never be interrupted allowing continuous burst transfers. Furthermore, uncached/direct memory accesses will be stalled until all cache operations are completed to ensure memory coherency.