m-mode tagging: Standardize support for m-mode tagging #15
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
Recent discussions in TG echoed that support for m-mode tagging should be standardized instead of leaving the enabling mechanism to be impl. dependent. This patch defines the enabling mechanism to be defined via `mseccfg` CSR and adds a CSR for holding base address for tag table. Maximum virtual address of M-mode is left impl. defined because priv spec doesn't define any standard mechanism to discover maximum addressable physical address on platform. Signed-off-by: Deepak Gupta <[email protected]>
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.
Recent discussions in TG echoed that support for m-mode tagging should be standardized instead of leaving the enabling mechanism to be impl. dependent. This patch defines the enabling mechanism to be defined via
mseccfgCSR and adds a CSR for holding base address for tag table. Maximum virtual address of M-mode is left impl. defined because priv spec doesn't define any standard mechanism to discover maximum addressable physical address on platform.