debug: Fix nonexistent trigger registers trap handle in entry.S #549
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.
In
Sv39Test,SV48Test, andSV57Test, if the processor does not implement the trigger module, accessing the trigger csr registers will result in a trap, causing themppfield inmstatusto be modified to machine mode. Additionally, in the original code,mstatusis not restored after trap, resulting in the effective privilege mode beingmachine modein subsequent translate tests, which prevents address translation and leads to test failures.This PR ensures that processors without implementing the trigger module can pass the tests successfully.