arch/csky/include/asm/kprobes.h

File Facts

System

Linux kernel

Corpus path

arch/csky/include/asm/kprobes.h

Extension

.h

Size

1158 bytes

Lines

49

Domain

Architecture Layer

Bucket

arch/csky

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-generic/kprobes.h
• linux/types.h
• linux/ptrace.h
• linux/percpu.h
• asm/probes.h

Detected Declarations

• struct prev_kprobe
• struct kprobe_step_ctx
• struct kprobe_ctlblk

Annotated Snippet

struct prev_kprobe {
	struct kprobe *kp;
	unsigned int status;
};

/* Single step context for kprobe */
struct kprobe_step_ctx {
	unsigned long ss_pending;
	unsigned long match_addr;
};

/* per-cpu kprobe control block */
struct kprobe_ctlblk {
	unsigned int kprobe_status;
	unsigned long saved_sr;
	struct prev_kprobe prev_kprobe;
	struct kprobe_step_ctx ss_ctx;
};

void arch_remove_kprobe(struct kprobe *p);
int kprobe_fault_handler(struct pt_regs *regs, unsigned int trapnr);
int kprobe_breakpoint_handler(struct pt_regs *regs);
int kprobe_single_step_handler(struct pt_regs *regs);
void __kretprobe_trampoline(void);
void __kprobes *trampoline_probe_handler(struct pt_regs *regs);

#endif /* CONFIG_KPROBES */
#endif /* __ASM_CSKY_KPROBES_H */

Annotation

• Immediate include surface: `asm-generic/kprobes.h`, `linux/types.h`, `linux/ptrace.h`, `linux/percpu.h`, `asm/probes.h`.
• Detected declarations: `struct prev_kprobe`, `struct kprobe_step_ctx`, `struct kprobe_ctlblk`.
• Atlas domain: Architecture Layer / arch/csky.
• 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.