arch/s390/kernel/lgr.c
Source file repositories/reference/linux-study-clean/arch/s390/kernel/lgr.c
File Facts
- System
- Linux kernel
- Corpus path
arch/s390/kernel/lgr.c- Extension
.c- Size
- 4377 bytes
- Lines
- 188
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/init.hlinux/export.hlinux/timer.hlinux/slab.hasm/facility.hasm/sysinfo.hasm/ebcdic.hasm/debug.hasm/ipl.h
Detected Declarations
struct lgr_infofunction cpasciifunction lgr_stsi_1_1_1function lgr_stsi_2_2_2function lgr_stsi_3_2_2function lgr_info_getfunction lgr_info_logfunction lgr_timer_fnfunction lgr_timer_setfunction lgr_initmodule init lgr_initexport lgr_info_log
Annotated Snippet
device_initcall(lgr_init);Annotation
- Immediate include surface: `linux/init.h`, `linux/export.h`, `linux/timer.h`, `linux/slab.h`, `asm/facility.h`, `asm/sysinfo.h`, `asm/ebcdic.h`, `asm/debug.h`.
- Detected declarations: `struct lgr_info`, `function cpascii`, `function lgr_stsi_1_1_1`, `function lgr_stsi_2_2_2`, `function lgr_stsi_3_2_2`, `function lgr_info_get`, `function lgr_info_log`, `function lgr_timer_fn`, `function lgr_timer_set`, `function lgr_init`.
- 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.