arch/s390/include/asm/kprobes.h

File Facts

System

Linux kernel

Corpus path

arch/s390/include/asm/kprobes.h

Extension

.h

Size

2073 bytes

Lines

81

Domain

Architecture Layer

Bucket

arch/s390

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

• linux/types.h
• asm/ctlreg.h
• asm-generic/kprobes.h
• linux/ptrace.h
• linux/percpu.h
• linux/sched/task_stack.h

Detected Declarations

• struct pt_regs
• struct kprobe
• struct arch_specific_insn
• struct prev_kprobe
• struct kprobe_ctlblk

Annotated Snippet

struct arch_specific_insn {
	/* copy of original instruction */
	kprobe_opcode_t *insn;
};

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

/* per-cpu kprobe control block */
struct kprobe_ctlblk {
	unsigned long kprobe_status;
	unsigned long kprobe_saved_imask;
	struct ctlreg kprobe_saved_ctl[3];
	struct prev_kprobe prev_kprobe;
};

void arch_remove_kprobe(struct kprobe *p);

int kprobe_fault_handler(struct pt_regs *regs, int trapnr);

#define flush_insn_slot(p)	do { } while (0)

#endif /* CONFIG_KPROBES */
#endif	/* _ASM_S390_KPROBES_H */

Annotation

• Immediate include surface: `linux/types.h`, `asm/ctlreg.h`, `asm-generic/kprobes.h`, `linux/ptrace.h`, `linux/percpu.h`, `linux/sched/task_stack.h`.
• Detected declarations: `struct pt_regs`, `struct kprobe`, `struct arch_specific_insn`, `struct prev_kprobe`, `struct kprobe_ctlblk`.
• Atlas domain: Architecture Layer / arch/s390.
• 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.