arch/microblaze/kernel/setup.c
Source file repositories/reference/linux-study-clean/arch/microblaze/kernel/setup.c
File Facts
- System
- Linux kernel
- Corpus path
arch/microblaze/kernel/setup.c- Extension
.c- Size
- 5305 bytes
- Lines
- 200
- Domain
- Architecture Layer
- Bucket
- arch/microblaze
- 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/of_clk.hlinux/clocksource.hlinux/string.hlinux/seq_file.hlinux/cpu.hlinux/initrd.hlinux/console.hlinux/debugfs.hlinux/of_fdt.hlinux/pgtable.hasm/setup.hasm/sections.hasm/page.hlinux/io.hlinux/bug.hlinux/param.hlinux/pci.hlinux/cache.hlinux/of.hlinux/dma-mapping.hasm/cacheflush.hasm/entry.hasm/cpuinfo.h
Detected Declarations
function setup_archfunction get_romfs_lenfunction machine_early_initfunction time_initfunction microblaze_debugfs_initfunction debugfs_tlbmodule init debugfs_tlb
Annotated Snippet
device_initcall(debugfs_tlb);
#endifAnnotation
- Immediate include surface: `linux/init.h`, `linux/of_clk.h`, `linux/clocksource.h`, `linux/string.h`, `linux/seq_file.h`, `linux/cpu.h`, `linux/initrd.h`, `linux/console.h`.
- Detected declarations: `function setup_arch`, `function get_romfs_len`, `function machine_early_init`, `function time_init`, `function microblaze_debugfs_init`, `function debugfs_tlb`, `module init debugfs_tlb`.
- Atlas domain: Architecture Layer / arch/microblaze.
- 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.