arch/m68k/kernel/syscalltable.S

File Facts

System

Linux kernel

Corpus path

arch/m68k/kernel/syscalltable.S

Extension

.S

Size

645 bytes

Lines

26

Domain

Architecture Layer

Bucket

arch/m68k

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.

Dependency Surface

• linux/linkage.h
• asm/syscall_table.h

Detected Declarations

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

Annotated Snippet

#include <linux/linkage.h>

#ifndef CONFIG_MMU
#define sys_mmap2	sys_mmap_pgoff
#endif

#define __SYSCALL(nr, entry) .long entry
	.section .rodata
ALIGN
ENTRY(sys_call_table)
#include <asm/syscall_table.h>

Annotation

• Immediate include surface: `linux/linkage.h`, `asm/syscall_table.h`.
• Atlas domain: Architecture Layer / arch/m68k.
• 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.