arch/s390/include/asm/abs_lowcore.h

File Facts

System

Linux kernel

Corpus path

arch/s390/include/asm/abs_lowcore.h

Extension

.h

Size

595 bytes

Lines

29

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/smp.h
• asm/lowcore.h

Detected Declarations

• function put_abs_lowcore

Annotated Snippet

#ifndef _ASM_S390_ABS_LOWCORE_H
#define _ASM_S390_ABS_LOWCORE_H

#include <linux/smp.h>
#include <asm/lowcore.h>

#define ABS_LOWCORE_MAP_SIZE	(NR_CPUS * sizeof(struct lowcore))

extern unsigned long __abs_lowcore;

int abs_lowcore_map(int cpu, struct lowcore *lc, bool alloc);
void abs_lowcore_unmap(int cpu);

static inline struct lowcore *get_abs_lowcore(void)
{
	int cpu;

	cpu = get_cpu();
	return ((struct lowcore *)__abs_lowcore) + cpu;
}

static inline void put_abs_lowcore(struct lowcore *lc)
{
	put_cpu();
}

#endif /* _ASM_S390_ABS_LOWCORE_H */

Annotation

• Immediate include surface: `linux/smp.h`, `asm/lowcore.h`.
• Detected declarations: `function put_abs_lowcore`.
• 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.