Allow alternative capability encodings #357
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
tariqkurd-repo
approved these changes
Sep 9, 2024
Co-authored-by: Tariq Kurd <tariqandlaura@gmail.com> Signed-off-by: Andres Amaya Garcia <andres.amaya@codasip.com>
jrtc27
reviewed
Sep 9, 2024
arichardson
reviewed
Sep 9, 2024
arichardson
reviewed
Sep 9, 2024
tariqkurd-repo
added a commit
to tariqkurd-repo/riscv-cheri
that referenced
this pull request
Oct 9, 2024
Allow implementations supporting CHERI RISC-V to use alternative capability encodings that provide most key features, such as bounds and permissions, but may change, for example, the granularity of bounds or offer additional features. Also, allow the `sentry` instruction to become an illegal when using alternative capability encodings that do not provide ambient sealing permission. The paragraph allowing alternative encodings is largely inspired from the paragraph in the RISC-V Privileged Specification that allows alternative privileged ISA designs. Fix riscv#324 --------- Signed-off-by: Andres Amaya Garcia <andres.amaya@codasip.com> Co-authored-by: Tariq Kurd <tariqandlaura@gmail.com>
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.
Allow implementations supporting CHERI RISC-V to use alternative capability encodings that provide most key features, such as bounds and permissions, but may change, for example, the granularity of bounds or offer additional features. Also, allow the
sentryinstruction to become an illegal when using alternative capability encodings that do not provide ambient sealing permission.The paragraph allowing alternative encodings is largely inspired from the paragraph in the RISC-V Privileged Specification that allows alternative privileged ISA designs.
Fix #324