arch/x86/include/asm/entry-common.h

File Facts

System

Linux kernel

Corpus path

arch/x86/include/asm/entry-common.h

Extension

.h

Size

2965 bytes

Lines

103

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/randomize_kstack.h
• linux/user-return-notifier.h
• asm/nospec-branch.h
• asm/io_bitmap.h
• asm/fpu/api.h
• asm/fred.h

Detected Declarations

• function arch_enter_from_user_mode
• function arch_exit_work
• function arch_exit_to_user_mode_prepare
• function this_cpu_read
• function arch_exit_to_user_mode

Annotated Snippet

this_cpu_read(x86_ibpb_exit_to_user)) {
		indirect_branch_prediction_barrier();
		this_cpu_write(x86_ibpb_exit_to_user, false);
	}
}
#define arch_exit_to_user_mode_prepare arch_exit_to_user_mode_prepare

static __always_inline void arch_exit_to_user_mode(void)
{
	amd_clear_divider();
}
#define arch_exit_to_user_mode arch_exit_to_user_mode

extern void x86_entry_from_kvm(unsigned int entry_type, unsigned int vector);

#endif

Annotation

• Immediate include surface: `linux/randomize_kstack.h`, `linux/user-return-notifier.h`, `asm/nospec-branch.h`, `asm/io_bitmap.h`, `asm/fpu/api.h`, `asm/fred.h`.
• Detected declarations: `function arch_enter_from_user_mode`, `function arch_exit_work`, `function arch_exit_to_user_mode_prepare`, `function this_cpu_read`, `function arch_exit_to_user_mode`.
• 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.