arch/loongarch/include/uapi/asm/break.h

File Facts

System

Linux kernel

Corpus path

arch/loongarch/include/uapi/asm/break.h

Extension

.h

Size

918 bytes

Lines

24

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.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __UAPI_ASM_BREAK_H
#define __UAPI_ASM_BREAK_H

#define BRK_DEFAULT		0	/* Used as default */
#define BRK_BUG			1	/* Used by BUG() */
#define BRK_KDB			2	/* Used in KDB_ENTER() */
#define BRK_MATHEMU		3	/* Used by FPU emulator */
#define BRK_USERBP		4	/* User bp (used by debuggers) */
#define BRK_SSTEPBP		5	/* User bp (used by debuggers) */
#define BRK_OVERFLOW		6	/* Overflow check */
#define BRK_DIVZERO		7	/* Divide by zero check */
#define BRK_RANGE		8	/* Range error check */
#define BRK_MULOVFL		9	/* Multiply overflow */
#define BRK_KPROBE_BP		10	/* Kprobe break */
#define BRK_KPROBE_SSTEPBP	11	/* Kprobe single step break */
#define BRK_UPROBE_BP		12	/* See <asm/uprobes.h> */
#define BRK_UPROBE_XOLBP	13	/* See <asm/uprobes.h> */

#endif /* __UAPI_ASM_BREAK_H */

Annotation

• 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.