igvmbuilder: configure XCR0 as expected in CPUID tables #511
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.
A recent change to the SVSM kernel requires XCR0 to match the value
1
when looking for CPUID[EAX=0Dh] leaves. However, the IGVM file builder was populating the CPUID template with XCR0=0, resulting in a mismatch when the CPUID lookup was attempted. This change sets XCR0=1 for the extended leaves in the CPUID template in the IGVM file so the constructed table matches the expected value at lookup time.