arch/powerpc/kernel/sys_ppc32.c

File Facts

System

Linux kernel

Corpus path

arch/powerpc/kernel/sys_ppc32.c

Extension

.c

Size

3954 bytes

Lines

136

Domain

Architecture Layer

Bucket

arch/powerpc

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/kernel.h
• linux/sched.h
• linux/fs.h
• linux/mm.h
• linux/file.h
• linux/signal.h
• linux/resource.h
• linux/times.h
• linux/smp.h
• linux/sem.h
• linux/msg.h
• linux/shm.h
• linux/poll.h
• linux/personality.h
• linux/stat.h
• linux/in.h
• linux/syscalls.h
• linux/unistd.h
• linux/sysctl.h
• linux/binfmts.h
• linux/security.h
• linux/compat.h
• linux/ptrace.h
• linux/elf.h
• linux/ipc.h
• linux/slab.h
• asm/ptrace.h
• asm/types.h
• linux/uaccess.h
• asm/unistd.h
• asm/time.h
• asm/mmu_context.h

Detected Declarations

• syscall ppc_fallocate
• function Copyright

Annotated Snippet

SYSCALL_DEFINE6(ppc_fallocate,
		int, fd, int, mode,
		u32, offset1, u32, offset2, u32, len1, u32, len2)
{
	return ksys_fallocate(fd, mode,
			      merge_64(offset1, offset2),
			      merge_64(len1, len2));
}
#endif

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/sched.h`, `linux/fs.h`, `linux/mm.h`, `linux/file.h`, `linux/signal.h`, `linux/resource.h`, `linux/times.h`.
• Detected declarations: `syscall ppc_fallocate`, `function Copyright`.
• Atlas domain: Architecture Layer / arch/powerpc.
• 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.