arch/s390/crypto/arch_random.c
Source file repositories/reference/linux-study-clean/arch/s390/crypto/arch_random.c
File Facts
- System
- Linux kernel
- Corpus path
arch/s390/crypto/arch_random.c- Extension
.c- Size
- 489 bytes
- Lines
- 21
- Domain
- Architecture Layer
- Bucket
- arch/s390
- Inferred role
- Architecture Layer: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
Dependency Surface
linux/export.hlinux/kernel.hlinux/atomic.hlinux/random.hlinux/static_key.hasm/archrandom.hasm/cpacf.h
Detected Declarations
export s390_arch_random_counter
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* s390 arch random implementation.
*
* Copyright IBM Corp. 2017, 2020
* Author(s): Harald Freudenberger
*/
#include <linux/export.h>
#include <linux/kernel.h>
#include <linux/atomic.h>
#include <linux/random.h>
#include <linux/static_key.h>
#include <asm/archrandom.h>
#include <asm/cpacf.h>
DEFINE_STATIC_KEY_FALSE(s390_arch_random_available);
atomic64_t s390_arch_random_counter = ATOMIC64_INIT(0);
EXPORT_SYMBOL(s390_arch_random_counter);
Annotation
- Immediate include surface: `linux/export.h`, `linux/kernel.h`, `linux/atomic.h`, `linux/random.h`, `linux/static_key.h`, `asm/archrandom.h`, `asm/cpacf.h`.
- Detected declarations: `export s390_arch_random_counter`.
- Atlas domain: Architecture Layer / arch/s390.
- Implementation status: integration 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.