Dev/preemption - #126
Draft
tom-kuchler wants to merge 7 commits into
Draft
Conversation
…o trigger preemption from outside
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
2 participants
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.
Adding preemption to the KVM backend.
Probably want to make a few more changes before fully merging.
Could also consider first splitting of the preemption mechanism as one PR, since that is generally useful and then looking at the low priority work separately.
One thing to consider is the way interrupts are sent to the running functions.
The "recommended" way in the KVM manual is installing a signal handler, that sets the VM to immediately exit if started.
If the VM is about to start, it will immediately exit, if it has already started, it will exit because of the interrupt handler.
(Documentation here: https://docs.kernel.org/virt/kvm/api.html#the-kvm-run-structure)