Added documentation regarding bkpt and related registers #38
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.
I have done some research around the breakpoint instruction and some of the undocumented registers that are intended to be used with it. I figured I should put my findings in the Addendum.
I'd like to bring some extra attention to this paragraph:
I am not sure this should be included at all. After all this is a Linux-specific problem; as a user space program we do not have access to hardware interrupts. However, it also begs the question whether direct scheduling could be added to
vcio2
in the future and whether it is possible to then bring IRQ functionality back, while retaining the option to run programs asynchronously or with very long timeouts.