arch/m68k/include/asm/ptrace.h
Source file repositories/reference/linux-study-clean/arch/m68k/include/asm/ptrace.h
File Facts
- System
- Linux kernel
- Corpus path
arch/m68k/include/asm/ptrace.h- Extension
.h- Size
- 645 bytes
- Lines
- 29
- Domain
- Architecture Layer
- Bucket
- arch/m68k
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
uapi/asm/ptrace.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _M68K_PTRACE_H
#define _M68K_PTRACE_H
#include <uapi/asm/ptrace.h>
#ifndef __ASSEMBLER__
#ifndef PS_S
#define PS_S (0x2000)
#define PS_M (0x1000)
#endif
#define user_mode(regs) (!((regs)->sr & PS_S))
#define instruction_pointer(regs) ((regs)->pc)
#define profile_pc(regs) instruction_pointer(regs)
#define current_pt_regs() \
(struct pt_regs *)((char *)current_thread_info() + THREAD_SIZE) - 1
#define current_user_stack_pointer() rdusp()
#define arch_has_single_step() (1)
#ifdef CONFIG_MMU
#define arch_has_block_step() (1)
#endif
#endif /* __ASSEMBLER__ */
#endif /* _M68K_PTRACE_H */
Annotation
- Immediate include surface: `uapi/asm/ptrace.h`.
- Atlas domain: Architecture Layer / arch/m68k.
- 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.