arch/x86/include/asm/vsyscall.h

File Facts

System

Linux kernel

Corpus path

arch/x86/include/asm/vsyscall.h

Extension

.h

Size

1111 bytes

Lines

43

Domain

Architecture Layer

Bucket

arch/x86

Inferred role

Architecture Layer: syscall or user/kernel boundary

Status

core 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 participates in a user/kernel boundary; inspect argument validation, copy_from_user/copy_to_user, credentials, and dispatch target.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/seqlock.h
• uapi/asm/vsyscall.h
• asm/page_types.h

Detected Declarations

• function map_vsyscall
• function emulate_vsyscall_gp
• function The

Annotated Snippet

static inline void map_vsyscall(void) {}
static inline bool emulate_vsyscall_pf(unsigned long error_code,
				       struct pt_regs *regs, unsigned long address)
{
	return false;
}

static inline bool emulate_vsyscall_gp(struct pt_regs *regs)
{
	return false;
}
#endif

/*
 * The (legacy) vsyscall page is the long page in the kernel portion
 * of the address space that has user-accessible permissions.
 */
static inline bool is_vsyscall_vaddr(unsigned long vaddr)
{
	return unlikely((vaddr & PAGE_MASK) == VSYSCALL_ADDR);
}

#endif /* _ASM_X86_VSYSCALL_H */

Annotation

• Immediate include surface: `linux/seqlock.h`, `uapi/asm/vsyscall.h`, `asm/page_types.h`.
• Detected declarations: `function map_vsyscall`, `function emulate_vsyscall_gp`, `function The`.
• Atlas domain: Architecture Layer / arch/x86.
• Implementation status: core 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.