arch/s390/include/asm/runtime_instr.h

File Facts

System

Linux kernel

Corpus path

arch/s390/include/asm/runtime_instr.h

Extension

.h

Size

634 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

• uapi/asm/runtime_instr.h

Detected Declarations

• struct task_struct
• function save_ri_cb
• function restore_ri_cb

Annotated Snippet

#ifndef _RUNTIME_INSTR_H
#define _RUNTIME_INSTR_H

#include <uapi/asm/runtime_instr.h>

extern struct runtime_instr_cb runtime_instr_empty_cb;

static inline void save_ri_cb(struct runtime_instr_cb *cb_prev)
{
	if (cb_prev)
		store_runtime_instr_cb(cb_prev);
}

static inline void restore_ri_cb(struct runtime_instr_cb *cb_next,
				 struct runtime_instr_cb *cb_prev)
{
	if (cb_next)
		load_runtime_instr_cb(cb_next);
	else if (cb_prev)
		load_runtime_instr_cb(&runtime_instr_empty_cb);
}

struct task_struct;

void runtime_instr_release(struct task_struct *tsk);

#endif /* _RUNTIME_INSTR_H */

Annotation

• Immediate include surface: `uapi/asm/runtime_instr.h`.
• Detected declarations: `struct task_struct`, `function save_ri_cb`, `function restore_ri_cb`.
• 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.