CPUID
Enable an agent to recognize CPUID, interpret processor capability reports in context, and decide which additional checks are needed before using those capabilities.
Bundle → Layer → Finding → Questions Filled
5 bundles · 9 layers · 15 findings · 23 questions
Instruction and query contract Identify the intended instruction and preserve the inputs needed to interpret each response.
Referent and interface
Resolve what CPUID denotes and establish its register-based interface.
Selector-dependent register interface
CPUID returns identification and feature information in EAX, EBX, ECX, and EDX. Model the instruction separately from each observation. Reference: [Intel architecture programming reference](https://www.intel.com/content/dam/develop/external/us/en/documents/architecture-instruction-set-extensions-programming-reference-737410.pdf).
- Does the registry's originating record identify the x86 instruction rather than the CPUID company or a utility? definition
- Which EAX leaf and applicable ECX subleaf produced this response? measurement
Enumeration boundaries
Determine which queries are meaningful and how enumeration terminates.
Range and subleaf validity
Standard and extended function ranges require explicit handling; retain range discovery and leaf-specific enumeration rules. Reference: [AMD CPUID specification](https://www.amd.com/content/dam/amd/en/documents/archived-tech-docs/design-guides/25481.pdf).
- What supported ranges and maximum selectors were observed? measurement
- Which documented validity and termination rules apply to this leaf's subleaves? boundary
Identity and decoding Interpret reported identity and register fields under the correct architectural authority.
Processor signature
Relate identification fields to documented processor classifications.
Family, model, and stepping interpretation
Processor signature interpretation requires documented family and model decoding rules. Reference: [Intel CPUID enumeration guidance](https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/technical-documentation/cpuid-enumeration-and-architectural-msrs.html).
- Which raw signature fields and vendor-specific rules support the decoded family, model, and stepping? provenance
- What evidence would be needed before associating this report with one physical asset? boundary
Field meaning and authority
Keep raw values distinct from named capabilities and interpretation revisions.
Traceable bit decoding
Each decoded claim should identify its leaf, subleaf, register, bit or field, and supporting specification; retain unrecognized fields without assigning invented meanings.
- Which document revision and field definition justify this decoded claim? provenance
- Is this field defined, reserved, or outside the decoder's supported scope? boundary
Reported capabilities and use Connect capability reports to software decisions and structural interpretations.
Feature dispatch prerequisites
Distinguish a reported processor capability from permission and readiness to execute dependent code.
Usable feature decision
Record the complete prerequisite check for a proposed code path, including applicable operating system extended-state enablement, rather than treating one feature bit as sufficient.
- Which CPUID fields and non-CPUID state checks does this code path require? action
- What fallback should the agent select when a prerequisite is absent or unverified? action
Topology and cache reports
Interpret structural reports with explicit units, scope, and derivation rules.
Structural report interpretation
For available topology and cache queries, retain raw fields and decoding formulas, and separate the reported structure from operating system availability and measured performance.
- Which queries and formulas support the reported cache dimensions or topology relationships? measurement
- How does the reported structure relate to the processors available to this process? boundary
Observation context and confidence Preserve where a report came from and determine how far its claims may be generalized.
Physical and virtual context
Attach observations to their logical processor and any known virtualization boundary.
Report origin and mediation
Record whether the report was collected directly, supplied by another tool, or obtained inside a virtual environment, and leave host hardware conclusions unresolved where mediation is unknown.
- Which collector, logical processor or vCPU, and execution environment produced the report? provenance
- What evidence establishes whether the reported capabilities reflect a guest-visible configuration or physical hardware? boundary
Coverage and revalidation
Determine whether collected evidence supports the intended decision and when it needs refreshing.
Decision-specific evidence coverage
Record missing queries, collection failures, and differences between processor observations; define revalidation conditions for decisions that depend on those reports.
- Does the report cover every selector and execution context required by the proposed decision? measurement
- Which changes to processor placement, virtual machine configuration, or system state require recollection? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of CPUID this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these identifiers and schemes hold for the sense of CPUID this model covers, and on what evidence? provenance
Standards and regulation
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these standards and regulation hold for the sense of CPUID this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of CPUID this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these typical measurements hold for the sense of CPUID this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these failure modes and hazards hold for the sense of CPUID this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of CPUID this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Information and virtual systems
- Entry kind
- thing
- Plane
- INF
- Domain
- INF.KNW
What it is Filled
CPUID is an x86 processor instruction that returns processor identification, capability and configuration information through registers selected by an input function number and, for some functions, a subfunction number.
In scope
- The CPUID instruction and its leaf and subleaf query interface
- Raw register responses and their documented interpretation
- Reported processor identity, features, topology, and cache information
- Vendor-specific enumeration rules and unsupported queries
- Execution context, virtualization, and capability decision prerequisites
Out of scope
- Processor hardware design, manufacture, and lifecycle
- The CPUID software company and its products
- Complete operating system processor initialization and scheduling
- Benchmark results and measured application performance
- General instruction set semantics beyond CPUID and its interpretation dependencies
- Hardware identity attestation and asset ownership records
Why it exists Filled
Enable an agent to recognize CPUID, interpret processor capability reports in context, and decide which additional checks are needed before using those capabilities.
Distinguishing features Filled
- Denotes an executable x86 instruction with selector-dependent register results, rather than a single permanent CPU identifier.
- Uses EAX to select a leaf and, for applicable leaves, ECX to select a subleaf; responses occupy EAX, EBX, ECX, and EDX.
- Reports processor identity and capability information rather than measuring instruction throughput or application speed.
- Its mnemonic names an architectural interface; a diagnostic utility that invokes it is a separate software artifact.
- A reported feature and a feature usable by the current process require separate judgments.
What robots and AI may and may not do Filled
Must not
- Use processor identification to fingerprint and track users without consent.
- Spoof processor information to evade licensing or security controls.
- Assume features are present without checking, risking crashes on other processors.
Only with a human decision
- Collecting hardware identifiers from users' machines.
May
- Query processor capabilities on systems it is authorized to run on and report them.
- Explain the instruction and its common leaves for developers.
Moral aspects Filled
- Hardware identifiers can be used to track people across services.
Who is affected
- Users of the computers
- Software developers
- Owners of the machines
Owners Filled
Steward
Nobody owns it; processor vendors document its behaviour.
Links to other meta-models Filled
parent
- Q20816930 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.cpuid
- Wikidata: Q1024235 (https://www.wikidata.org/wiki/Q1024235)
Direct properties not applicable Not applicable
- Referent interpretation: x86 instruction; unresolved alternative referent
- Query selector: 32-bit EAX leaf and applicable 32-bit ECX subleaf, represented in hexadecimal
- Raw response: Four unsigned 32-bit register values: EAX, EBX, ECX, EDX
- Enumeration coverage: complete for declared scope; partial; unavailable; unknown
- Reported processor identity: Vendor string, applicable family/model/stepping fields, optional brand string
- Feature evidence state: reported present; reported absent; unqueried; reserved; undecoded
- Execution context: Observation linked to logical processor or vCPU, process environment, and collection time
- Decode authority: Vendor manual, revision, section, and applicable processor or interface scope
- Capability usability: usable after checks; prerequisite missing; unsupported; undetermined
Plane INF: no invented physical properties.
Recognition optional Filled
- Appears in assembly code as the cpuid mnemonic, with a leaf number placed in the EAX register.
Capabilities and actions required Filled
- Collect a bounded CPUID report while retaining query selectors and raw registers.
- Decode identity and capability fields against an applicable vendor specification.
- Determine which leaves and subleaves require further enumeration.
- Compare reports across logical processors or execution environments.
- Evaluate a software feature's prerequisites before selecting an implementation.
- Flag incomplete, contradictory, or context-dependent reports for investigation.
Hazards and failure modes required Filled
- Misread feature flags lead programs to crash on unsupported processors.
- Virtual machines may report misleading values.
Standards and interfaces not applicable Not applicable
Not applicable
The instruction interface is defined by processor architecture specifications rather than an independently issued standard, law or official classification.
Context of use required Filled
- CPUID is used by operating systems, hypervisors, diagnostic programs and application libraries on x86 processors.
- Its reported information supports processor identification, capability discovery and selection of compatible software execution paths.
- Reported hardware capabilities may require additional operating system support checks before software can use them.
Sources Filled
- Wikidata item Q1024235: CPUID - identity and sense of the item
- Wikipedia: CPUID - general description of the item
Open questions
- Does the originating registry record confirm the x86 instruction as the referent, and why was it assigned to INF.MED?
- Does an existing Vercy world model already own CPUID or its processor capability enumeration contract?
- Which processor vendors, architectural generations, and specification revisions should the first researched publication support?
- Which hypervisor interfaces and vendor-specific leaves need explicit coverage, and which should remain extensions?
- What minimum collection and operating system state evidence is required before an agent may approve a feature-dependent code path?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q1024235/spec.json