Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce GCTYPE to obtain the capability type #337

Merged
merged 1 commit into from
Aug 23, 2024

Conversation

arichardson
Copy link
Collaborator

While the base CHERI specification only has unsealed capabilities and one type of sentry capability, other extensions (e.g. CherIoT) that will build upon the base CHERI-RISC-V standard have additional types of capabilities. Defining the specification in terms of object types instead of just having unsealed and sentry is one important step towards allowing CherIoT to be a RV32E extension on top of the base standard.

See https://lists.riscv.org/g/tech-tg-cheri/message/6

@arichardson
Copy link
Collaborator Author

@davidchisnall @nwf I haven't yet updated the semantics of sealing but hopefully you agree this is a correct first step.

@arichardson arichardson requested a review from jrtc27 August 1, 2024 17:04
Copy link

@nwf-msr nwf-msr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

src/insns/gctype_32bit.adoc Show resolved Hide resolved
While the base CHERI specification only has unsealed capabilities and
one type of sentry capability, other extensions (e.g. CherIoT) that
will build upon the base CHERI-RISC-V standard have additional types of
capabilities. Defining the specification in terms of object types
instead of just having unsealed and sentry is one important step towards
allowing CherIoT to be a RV32E extension on top of the base standard.

See https://lists.riscv.org/g/tech-tg-cheri/message/6
@arichardson arichardson enabled auto-merge (squash) August 23, 2024 19:32
@arichardson arichardson merged commit 18ee512 into riscv:main Aug 23, 2024
2 checks passed
@arichardson arichardson deleted the gettype branch August 23, 2024 19:33
tariqkurd-repo pushed a commit to tariqkurd-repo/riscv-cheri that referenced this pull request Oct 9, 2024
While the base CHERI specification only has unsealed capabilities and
one type of sentry capability, other extensions (e.g. CherIoT) that will
build upon the base CHERI-RISC-V standard have additional types of
capabilities. Defining the specification in terms of object types
instead of just having unsealed and sentry is one important step towards
allowing CherIoT to be a RV32E extension on top of the base standard.

See https://lists.riscv.org/g/tech-tg-cheri/message/6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants