Kernel/riscv64: Handle breakpoint traps #24094
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
github-actions
bot
added
the
👀 pr-needs-review
This means that userspace breakpoint traps no longer panic the kernel. This also causes us to no longer panic on failed assertions in userspace when using gcc, as gcc compiles __builtin_trap to breakpoint instructions on RISC-V.
spholz
force-pushed
the
riscv-handle-ebreak
branch
from
45d5be2
to
dfb1401
Compare
ADKaster
approved these changes
May 23, 2024
github-actions
bot
removed
the
👀 pr-needs-review
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.
This means that userspace breakpoint traps no longer panic the kernel. This also causes us to no longer panic on failed assertions in userspace when using gcc, as gcc compiles __builtin_trap to breakpoint instructions on RISC-V.