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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

1025 bytes

Lines

41

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

• enum perf_event_loongarch_regs

Annotated Snippet

#ifndef _ASM_LOONGARCH_PERF_REGS_H
#define _ASM_LOONGARCH_PERF_REGS_H

enum perf_event_loongarch_regs {
	PERF_REG_LOONGARCH_PC,
	PERF_REG_LOONGARCH_R1,
	PERF_REG_LOONGARCH_R2,
	PERF_REG_LOONGARCH_R3,
	PERF_REG_LOONGARCH_R4,
	PERF_REG_LOONGARCH_R5,
	PERF_REG_LOONGARCH_R6,
	PERF_REG_LOONGARCH_R7,
	PERF_REG_LOONGARCH_R8,
	PERF_REG_LOONGARCH_R9,
	PERF_REG_LOONGARCH_R10,
	PERF_REG_LOONGARCH_R11,
	PERF_REG_LOONGARCH_R12,
	PERF_REG_LOONGARCH_R13,
	PERF_REG_LOONGARCH_R14,
	PERF_REG_LOONGARCH_R15,
	PERF_REG_LOONGARCH_R16,
	PERF_REG_LOONGARCH_R17,
	PERF_REG_LOONGARCH_R18,
	PERF_REG_LOONGARCH_R19,
	PERF_REG_LOONGARCH_R20,
	PERF_REG_LOONGARCH_R21,
	PERF_REG_LOONGARCH_R22,
	PERF_REG_LOONGARCH_R23,
	PERF_REG_LOONGARCH_R24,
	PERF_REG_LOONGARCH_R25,
	PERF_REG_LOONGARCH_R26,
	PERF_REG_LOONGARCH_R27,
	PERF_REG_LOONGARCH_R28,
	PERF_REG_LOONGARCH_R29,
	PERF_REG_LOONGARCH_R30,
	PERF_REG_LOONGARCH_R31,
	PERF_REG_LOONGARCH_MAX,
};
#endif /* _ASM_LOONGARCH_PERF_REGS_H */

Annotation

• Detected declarations: `enum perf_event_loongarch_regs`.
• 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.