NMI spec updates: removed UNMI, added new mnie bit to mnstatus #2904
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.
Related issue:
Type of change: bug report | feature request | other enhancement
Impact: API modification
Development Phase: implementation
Release Notes
The NMI arch spec is being prepared for submission to RISC-V International. As part of that, the UNMI feature has been removed from it. External IO unmi_* were removed and all internal implementation referring to unmi was removed. Most changes are in the CSR modules where NMI is processed.
The latest NMI spec has added a bit
mnie
(notnmie
) tomnstatus
. This bit reflects the internalrnmie
state.rnmie
is set at reset, is cleared when an NMI is taken, and is set by executingmnret
at the end of the NMI handler (unchanged by this PR). Nowrnmie
can also be read and set by software so that nested NMIs can be processed.rnmie
cannot be cleared by software, per the spec.The mnstatus register read value was using
io.status.mpp
(=mstatus.mpp
) instead ofmnstatus.mpp
.