RFC: virt: Replace generic VpHaltReasons with new CpuIo::fatal_error, add configurable policy #1911
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.
The intention behind this change is to provide better crash stacks and dumps in ICMs. By panicking at the point of error construction, rather than after the error has bubbled up to a higher layer, we are better able to capture stack context around the cause of the failure and to provide a meaningful stack to Watson (instead of just blaming the HaltRequest::Panic handler for all these different error sources). Essentially simulating 'unwrapping' these errors.
However the ability to keep a VM 'alive' for inspection after a failure is still useful, and we want to preserve it. Therefore this change makes this new behavior configurable.