arch/loongarch/include/asm/uprobes.h

File Facts

System

Linux kernel

Corpus path

arch/loongarch/include/asm/uprobes.h

Extension

.h

Size

927 bytes

Lines

36

Domain

Architecture Layer

Bucket

arch/loongarch

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/inst.h

Detected Declarations

• struct arch_uprobe
• struct arch_uprobe_task
• function uprobe_breakpoint_handler
• function uprobe_singlestep_handler

Annotated Snippet

struct arch_uprobe {
	u32	insn[2];
	u32	ixol[2];
	bool	simulate;
};

struct arch_uprobe_task {
	unsigned long saved_trap_nr;
};

#ifdef CONFIG_UPROBES
bool uprobe_breakpoint_handler(struct pt_regs *regs);
bool uprobe_singlestep_handler(struct pt_regs *regs);
#else /* !CONFIG_UPROBES */
static inline bool uprobe_breakpoint_handler(struct pt_regs *regs) { return false; }
static inline bool uprobe_singlestep_handler(struct pt_regs *regs) { return false; }
#endif /* CONFIG_UPROBES */

#endif /* __ASM_LOONGARCH_UPROBES_H */

Annotation

• Immediate include surface: `asm/inst.h`.
• Detected declarations: `struct arch_uprobe`, `struct arch_uprobe_task`, `function uprobe_breakpoint_handler`, `function uprobe_singlestep_handler`.
• Atlas domain: Architecture Layer / arch/loongarch.
• 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.