arch/x86/include/asm/spec-ctrl.h

File Facts

System

Linux kernel

Corpus path

arch/x86/include/asm/spec-ctrl.h

Extension

.h

Size

3089 bytes

Lines

102

Domain

Architecture Layer

Bucket

arch/x86

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

Dependency Surface

• linux/thread_info.h
• asm/nospec-branch.h
• asm/msr.h

Detected Declarations

• function x86_spec_ctrl_set_guest
• function x86_spec_ctrl_restore_host
• function ssbd_tif_to_spec_ctrl
• function stibp_tif_to_spec_ctrl
• function ssbd_spec_ctrl_to_tif
• function stibp_spec_ctrl_to_tif
• function ssbd_tif_to_amd_ls_cfg
• function __update_spec_ctrl
• function speculative_store_bypass_ht_init

Annotated Snippet

static inline void speculative_store_bypass_ht_init(void) { }
#endif

extern void speculation_ctrl_update(unsigned long tif);
extern void speculation_ctrl_update_current(void);

extern bool itlb_multihit_kvm_mitigation;

#endif

Annotation

• Immediate include surface: `linux/thread_info.h`, `asm/nospec-branch.h`, `asm/msr.h`.
• Detected declarations: `function x86_spec_ctrl_set_guest`, `function x86_spec_ctrl_restore_host`, `function ssbd_tif_to_spec_ctrl`, `function stibp_tif_to_spec_ctrl`, `function ssbd_spec_ctrl_to_tif`, `function stibp_spec_ctrl_to_tif`, `function ssbd_tif_to_amd_ls_cfg`, `function __update_spec_ctrl`, `function speculative_store_bypass_ht_init`.
• Atlas domain: Architecture Layer / arch/x86.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.