Repository navigation
Expose portable CPUID configuration for x86 machines - #211
Merged
Merged
Conversation
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
1 participant
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.
Machine models need to control the CPUID features presented to an x86 guest. Add an owned, portable CPUID entry table and expose supported-leaf enumeration and pre-execution configuration through
hypervisor.X86, implemented by KVM. Feature and topology policy stays with the caller.Validation:
GOWORK=off go test ./hypervisorand its race run pass. The trex consumer executes the configured CPUID and BIOS disk calls in a real KVM guest; fresh NT 3.1 through Windows 2000 integration checks pass. The broader internal KVM test package could not run locally because its generated FreeBSD guest-init embed payload is absent.