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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

887 bytes

Lines

45

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.

Dependency Surface

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

Detected Declarations

• enum perf_event_s390_regs

Annotated Snippet

#ifndef _ASM_S390_PERF_REGS_H
#define _ASM_S390_PERF_REGS_H

enum perf_event_s390_regs {
	PERF_REG_S390_R0,
	PERF_REG_S390_R1,
	PERF_REG_S390_R2,
	PERF_REG_S390_R3,
	PERF_REG_S390_R4,
	PERF_REG_S390_R5,
	PERF_REG_S390_R6,
	PERF_REG_S390_R7,
	PERF_REG_S390_R8,
	PERF_REG_S390_R9,
	PERF_REG_S390_R10,
	PERF_REG_S390_R11,
	PERF_REG_S390_R12,
	PERF_REG_S390_R13,
	PERF_REG_S390_R14,
	PERF_REG_S390_R15,
	PERF_REG_S390_FP0,
	PERF_REG_S390_FP1,
	PERF_REG_S390_FP2,
	PERF_REG_S390_FP3,
	PERF_REG_S390_FP4,
	PERF_REG_S390_FP5,
	PERF_REG_S390_FP6,
	PERF_REG_S390_FP7,
	PERF_REG_S390_FP8,
	PERF_REG_S390_FP9,
	PERF_REG_S390_FP10,
	PERF_REG_S390_FP11,
	PERF_REG_S390_FP12,
	PERF_REG_S390_FP13,
	PERF_REG_S390_FP14,
	PERF_REG_S390_FP15,
	PERF_REG_S390_MASK,
	PERF_REG_S390_PC,

	PERF_REG_S390_MAX
};

#endif /* _ASM_S390_PERF_REGS_H */

Annotation

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