arch/alpha/include/asm/asm-prototypes.h

File Facts

System

Linux kernel

Corpus path

arch/alpha/include/asm/asm-prototypes.h

Extension

.h

Size

505 bytes

Lines

20

Domain

Architecture Layer

Bucket

arch/alpha

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/spinlock.h
• asm/checksum.h
• asm/console.h
• asm/page.h
• asm/string.h
• linux/uaccess.h
• asm-generic/asm-prototypes.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#include <linux/spinlock.h>

#include <asm/checksum.h>
#include <asm/console.h>
#include <asm/page.h>
#include <asm/string.h>
#include <linux/uaccess.h>

#include <asm-generic/asm-prototypes.h>

extern void __divl(void);
extern void __reml(void);
extern void __divq(void);
extern void __remq(void);
extern void __divlu(void);
extern void __remlu(void);
extern void __divqu(void);
extern void __remqu(void);
extern unsigned long __udiv_qrnnd(unsigned long *, unsigned long, unsigned long , unsigned long);

Annotation

• Immediate include surface: `linux/spinlock.h`, `asm/checksum.h`, `asm/console.h`, `asm/page.h`, `asm/string.h`, `linux/uaccess.h`, `asm-generic/asm-prototypes.h`.
• Atlas domain: Architecture Layer / arch/alpha.
• 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.