arch/um/drivers/random.c

File Facts

System

Linux kernel

Corpus path

arch/um/drivers/random.c

Extension

.c

Size

2531 bytes

Lines

122

Domain

Architecture Layer

Bucket

arch/um

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/sched/signal.h
• linux/module.h
• linux/fs.h
• linux/interrupt.h
• linux/miscdevice.h
• linux/hw_random.h
• linux/delay.h
• linux/uaccess.h
• init.h
• irq_kern.h
• os.h

Detected Declarations

• function rng_dev_read
• function random_interrupt
• function rng_init
• function cleanup
• function rng_cleanup
• module init rng_init

Annotated Snippet

module_init (rng_init);
module_exit (rng_cleanup);
__uml_exitcall(cleanup);

MODULE_DESCRIPTION("UML Host Random Number Generator (RNG) driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/sched/signal.h`, `linux/module.h`, `linux/fs.h`, `linux/interrupt.h`, `linux/miscdevice.h`, `linux/hw_random.h`, `linux/delay.h`, `linux/uaccess.h`.
• Detected declarations: `function rng_dev_read`, `function random_interrupt`, `function rng_init`, `function cleanup`, `function rng_cleanup`, `module init rng_init`.
• Atlas domain: Architecture Layer / arch/um.
• Implementation status: integration implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.