CSR: use the guest-visible interrupt cause for VS-mode vectored dispatch - #3821
Open
PorterLu wants to merge 1 commit into
Open
CSR: use the guest-visible interrupt cause for VS-mode vectored dispatch#3821PorterLu wants to merge 1 commit into
PorterLu wants to merge 1 commit into
Conversation
vscause records the guest-visible cause code (SSI=1, STI=5, SEI=9), but the vector offset was derived from the HS-view code (VSSI=2, VSTI=6, VSEI=10). A guest in vectored mode therefore entered handler entry N+1 while vscause read N, with nothing to indicate the misdispatch.
This file contains hidden or 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.
vscause records the guest-visible cause code (SSI=1, STI=5, SEI=9), but the vector offset was derived from the HS-view code (VSSI=2, VSTI=6, VSEI=10). A guest in vectored mode therefore entered handler entry N+1 while vscause read N, with nothing to indicate the misdispatch.
Related issue: none
Type of change: bug report
Impact: functional fix
Development Phase: implementation