arch/x86/include/asm/hardirq.h

Source file repositories/reference/linux-study-clean/arch/x86/include/asm/hardirq.h

File Facts

System: Linux kernel
Corpus path: arch/x86/include/asm/hardirq.h
Extension: .h
Size: 2922 bytes
Lines: 117
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.
Touches IRQ or DMA behavior; this matters for the representative real-device path.
Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

linux/threads.h

Detected Declarations

enum irq_stat_counts
function kvm_set_cpu_l1tf_flush_l1d
function kvm_clear_cpu_l1tf_flush_l1d
function kvm_get_cpu_l1tf_flush_l1d
function kvm_set_cpu_l1tf_flush_l1d

Annotated Snippet

static __always_inline void kvm_set_cpu_l1tf_flush_l1d(void) { }
#endif /* IS_ENABLED(CONFIG_KVM_INTEL) */

#endif /* _ASM_X86_HARDIRQ_H */

Annotation

Immediate include surface: `linux/threads.h`.
Detected declarations: `enum irq_stat_counts`, `function kvm_set_cpu_l1tf_flush_l1d`, `function kvm_clear_cpu_l1tf_flush_l1d`, `function kvm_get_cpu_l1tf_flush_l1d`, `function kvm_set_cpu_l1tf_flush_l1d`.
Atlas domain: Architecture Layer / arch/x86.
Implementation status: source implementation candidate.
IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.