arch/m68k/include/asm/syscalls.h

File Facts

System

Linux kernel

Corpus path

arch/m68k/include/asm/syscalls.h

Extension

.h

Size

653 bytes

Lines

20

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.

Dependency Surface

• linux/compiler_types.h
• linux/linkage.h
• asm-generic/syscalls.h

Detected Declarations

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

Annotated Snippet

#ifndef _ASM_M68K_SYSCALLS_H
#define _ASM_M68K_SYSCALLS_H

#include <linux/compiler_types.h>
#include <linux/linkage.h>

asmlinkage int sys_cacheflush(unsigned long addr, int scope, int cache,
			      unsigned long len);
asmlinkage int sys_atomic_cmpxchg_32(unsigned long newval, int oldval, int d3,
				     int d4, int d5, unsigned long __user *mem);
asmlinkage int sys_getpagesize(void);
asmlinkage unsigned long sys_get_thread_area(void);
asmlinkage int sys_set_thread_area(unsigned long tp);
asmlinkage int sys_atomic_barrier(void);

#include <asm-generic/syscalls.h>

#endif	/* _ASM_M68K_SYSCALLS_H */

Annotation

• Immediate include surface: `linux/compiler_types.h`, `linux/linkage.h`, `asm-generic/syscalls.h`.
• Atlas domain: Architecture Layer / arch/m68k.
• Implementation status: core implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.