Launch guest APs in wait-for-ipi state #106
Closed
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
The FS base now holds the address of the start of the per-core section, instead of the core id
|
Hmm, it looks like under some circumstances the guest AP vmlaunch fails. Tracking that down now |
|
Closing in favor of #107 |
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.
Fixes #86
This MR gets guest application processors into the wait for IPI state. Note that the guest will not actually send the startup IPI to start using the APs, but they are available. This PR also fixes a few issues with percore variables that caused crashes on higher core counts. I've now tested this with an 8 core guest and things seem ok.