arch/powerpc/include/asm/syscall_wrapper.h

File Facts

System

Linux kernel

Corpus path

arch/powerpc/include/asm/syscall_wrapper.h

Extension

.h

Size

1670 bytes

Lines

50

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• struct pt_regs

Annotated Snippet

#define SYSCALL_DEFINE0(sname)							\
	SYSCALL_METADATA(_##sname, 0);						\
	long sys_##sname(const struct pt_regs *__unused);		\
	ALLOW_ERROR_INJECTION(sys_##sname, ERRNO);			\
	long sys_##sname(const struct pt_regs *__unused)

#define COND_SYSCALL(name)							\
	long sys_##name(const struct pt_regs *regs);			\
	long __weak sys_##name(const struct pt_regs *regs)		\
	{									\
		return sys_ni_syscall();					\
	}

#endif // __ASM_POWERPC_SYSCALL_WRAPPER_H

Annotation

• Detected declarations: `struct pt_regs`.
• 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.