arch/s390/include/asm/skey.h

File Facts

System

Linux kernel

Corpus path

arch/s390/include/asm/skey.h

Extension

.h

Size

725 bytes

Lines

33

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

• asm/rwonce.h

Detected Declarations

• struct skey_region
• function skey_regions_initialize

Annotated Snippet

struct skey_region {
	unsigned long start;
	unsigned long end;
};

#define SKEY_REGION(_start, _end)			\
	stringify_in_c(.section .skey_region,"a";)	\
	stringify_in_c(.balign 8;)			\
	stringify_in_c(.quad (_start);)			\
	stringify_in_c(.quad (_end);)			\
	stringify_in_c(.previous)

extern int skey_regions_initialized;
extern struct skey_region __skey_region_start[];
extern struct skey_region __skey_region_end[];

void __skey_regions_initialize(void);

static inline void skey_regions_initialize(void)
{
	if (READ_ONCE(skey_regions_initialized))
		return;
	__skey_regions_initialize();
}

#endif /* __ASM_SKEY_H */

Annotation

• Immediate include surface: `asm/rwonce.h`.
• Detected declarations: `struct skey_region`, `function skey_regions_initialize`.
• 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.