Skip to content

[Bug]: numerous bits are missing from the SDM list of mutable CPUID bits #21

Open

Description

@ludloff

SDM 092 Vol 1 table 21-1/21-2 on pages 21-3/21-4 (441/442 of 600) in section 21.1.5 lists mutable CPUID fields.

CPUID leaf 6 register EAX bit 1 (DA/turbo) is missing. It's mutable due to MISC_ENABLE[38].

CPUID leaf 7 sub leaf 0 register EBX bits 11 (RTM) and 7 (HLE) are missing. They're mutable due to TSX_CTRL[1].

CPUID leaf 7 sub leaf 0 register EDX bit 16 (TSXLDTRK) might be missing. It might be mutable due to TSX_CTRL[1]. (Please clarify this one.)

Also, numerous CPUID leaf 6 register EAX bits (related to HWP) are missing. They're mutable due to various MSR_MISC_PWR_MGMT bits – see SDM vol 4.

Activity

  1. ludloff commented on Sep 19, 2026

    @ludloff
    Author

    As for mutable CPUID bits due to MSR_MISC_PWR_MGMT bits...

    CPUID leaf 6 register ECX bit 3 – MSR_MISC_PWR_MGMT[1]

    CPUID leaf 6 register EAX bit 7 – MSR_MISC_PWR_MGMT[1] and [6]
    CPUID leaf 6 register EAX bit 8 – MSR_MISC_PWR_MGMT[7]
    CPUID leaf 6 register EAX bit 10 – MSR_MISC_PWR_MGMT[12]

    poorly documented CPUID bit – MSR_MISC_PWR_MGMT[8] – SDM vol 4 "ENABLE_OUT_OF_BAND_AUTONOMOUS
    Setting this bit will cause the HWP Autonomous feature bit to report as present; clearing will report as non-present."

  2. added
    SDM PDF issueThis problem is present in the SDM PDF and is/may be present in the website as a consequence
    on Sep 19, 2026
  3. ludloff commented on Sep 21, 2026

    @ludloff
    Author

    There are more cases.

    Visit https://www.sandpile.org/x86/cpuid.htm and search for "mutable" to find them all.

    Also, see this LKML msg, for a Q about AES-NI being mutable.

  4. alastairreid commented on Sep 29, 2026

    @alastairreid
    Contributor

    Hi @ludloff,

    [I just realized that I hadn't actually replied to your reports....]

    Thank you for this report - really useful and we are starting to work on this and your other reports.

    I don't directly work on the PDF version of the SDM so I'm handing these over to my team-mates who work on that (but not the executable spec, the website, etc.)
    I think that using github for reports that affect the PDF version of the SDM will be easier both for you and for us but it's taking us a moment to figure out how to integrate it with our existing Jira-based flow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    SDM PDF issueThis problem is present in the SDM PDF and is/may be present in the website as a consequence

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions