fix(PTW): clear reg after resp to prevent problem #4098
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.
PTW use reg full_gvpn_reg to generate GPF for out-of-range gpaddr, but this reg is not cleared after PTW response. If the last PTW request got a bad full_gvpn_reg, the gvpn_gpf and guestFault keeps until next PTW request, resulting in the total mess of state machine.
This patch clears full_gvpn_reg at the response of PTW. As PTW could response in two state paths, this patch adds an independent condition to achieve this.