arch/riscv/include/asm/uprobes.h
Source file repositories/reference/linux-study-clean/arch/riscv/include/asm/uprobes.h
File Facts
- System
- Linux kernel
- Corpus path
arch/riscv/include/asm/uprobes.h- Extension
.h- Size
- 1065 bytes
- Lines
- 52
- Domain
- Architecture Layer
- Bucket
- arch/riscv
- 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
asm/probes.hasm/text-patching.hasm/bug.h
Detected Declarations
struct arch_uprobe_taskstruct arch_uprobefunction uprobe_breakpoint_handlerfunction uprobe_single_step_handler
Annotated Snippet
struct arch_uprobe_task {
unsigned long saved_cause;
};
struct arch_uprobe {
union {
u8 insn[MAX_UINSN_BYTES];
u8 ixol[MAX_UINSN_BYTES];
};
struct arch_probe_insn api;
unsigned long insn_size;
bool simulate;
};
#ifdef CONFIG_UPROBES
bool uprobe_breakpoint_handler(struct pt_regs *regs);
bool uprobe_single_step_handler(struct pt_regs *regs);
#else
static inline bool uprobe_breakpoint_handler(struct pt_regs *regs)
{
return false;
}
static inline bool uprobe_single_step_handler(struct pt_regs *regs)
{
return false;
}
#endif /* CONFIG_UPROBES */
#endif /* _ASM_RISCV_UPROBES_H */
Annotation
- Immediate include surface: `asm/probes.h`, `asm/text-patching.h`, `asm/bug.h`.
- Detected declarations: `struct arch_uprobe_task`, `struct arch_uprobe`, `function uprobe_breakpoint_handler`, `function uprobe_single_step_handler`.
- Atlas domain: Architecture Layer / arch/riscv.
- 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.