Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

igvmbuilder: configure XCR0 as expected in CPUID tables #511

Merged
merged 2 commits into from
Nov 11, 2024
Merged

igvmbuilder: configure XCR0 as expected in CPUID tables #511

merged 2 commits into from
Nov 11, 2024

Commits on Nov 8, 2024

  1. igvmbuilder: configure XCR0 as expected in CPUID tables 

    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.

Signed-off-by: Jon Lange <[email protected]>
    @msft-jlange
    msft-jlange committed Nov 8, 2024
    Configuration menu
    Copy the full SHA
    fa17cc8 View commit details
    Browse the repository at this point in the history

Commits on Nov 10, 2024

  1. cpu/sse: use correct CPUID information to detect extended state support 

    The set of available extended features (XFEM/XCR0) is enumerated by
CPUID[EAX=0Dh,ECX=00h].EAX.  The set of available XSAVE features (e.g.
XSAVEOPT, XSAVEC) is enumerated by CPUID[EAX=0Dh,ECX=01h].EAX.  The
previous code had the CPUID detection inverted.

Signed-off-by: Jon Lange <[email protected]>
    @msft-jlange
    msft-jlange committed Nov 10, 2024
    Configuration menu
    Copy the full SHA
    5e64c55 View commit details
    Browse the repository at this point in the history