🧪 [pmp] use time-multiplex approach #1105
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
reducing hardware costs by ~50%
stnolting
added
HW
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.
Instruction dispatch (getting the next instruction word for execution) and load/store accesses cannot happen at the same time due to the multi-cycle architecture of the CPU. Therefore, checking PMP (physical memory protection) permissions of instruction fetch and load/store access in parallel brings no benefit. Actually, it is quite inefficient as the PMP needs to replicate all the logic to do two look-ups in parallel.
This PR changes the PMP architecture to use a time-multiplex approach. The actual PMP permission/region check is simplified to a single "issue" that is time-multiplexed between instruction and data access.
As always, any kind of feedback is highly appreciated.