arch/arm64/include/asm/uprobes.h

File Facts

System

Linux kernel

Corpus path

arch/arm64/include/asm/uprobes.h

Extension

.h

Size

868 bytes

Lines

43

Domain

Architecture Layer

Bucket

arch/arm64

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/debug-monitors.h
• asm/insn.h
• asm/probes.h

Detected Declarations

• struct arch_uprobe_task
• struct arch_uprobe
• function uprobe_single_step_handler

Annotated Snippet

struct arch_uprobe_task {
};

struct arch_uprobe {
	union {
		__le32 insn;
		__le32 ixol;
	};
	struct arch_probe_insn api;
	bool simulate;
};

int uprobe_brk_handler(struct pt_regs *regs, unsigned long esr);
#ifdef CONFIG_UPROBES
int uprobe_single_step_handler(struct pt_regs *regs, unsigned long esr);
#else
static inline int uprobe_single_step_handler(struct pt_regs *regs,
	unsigned long esr)
{
	return DBG_HOOK_ERROR;
}
#endif

#endif

Annotation

• Immediate include surface: `asm/debug-monitors.h`, `asm/insn.h`, `asm/probes.h`.
• Detected declarations: `struct arch_uprobe_task`, `struct arch_uprobe`, `function uprobe_single_step_handler`.
• Atlas domain: Architecture Layer / arch/arm64.
• 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.