Introduce integrity-fault exception #137
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
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.
The RISC-V Architecture Review Committee has discussed adding to
the forthcoming Privileged ISA version 1.13 exception cause codes for
synchronous exceptions due control flow integrity (CFI) checks,
among other possible, related triggers.
cause code
18 = integrity fault
On an integrity fault (code 18), the value automatically written to the
*tval CSR won't be an address but rather an additional numeric code:
*tval
2 = landing pad fault (extension Zicfilp)
3 = shadow stack fault (extension Zicfiss)
others reserved