arch/mips/kernel/mips-mt.c
Source file repositories/reference/linux-study-clean/arch/mips/kernel/mips-mt.c
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/kernel/mips-mt.c- Extension
.c- Size
- 3567 bytes
- Lines
- 164
- Domain
- Architecture Layer
- Bucket
- arch/mips
- 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/device.hlinux/kernel.hlinux/sched.hlinux/export.hlinux/interrupt.hlinux/security.hasm/cpu.hasm/processor.hlinux/atomic.hasm/hardirq.hasm/mmu_context.hasm/mipsmtregs.hasm/r4kcache.hasm/cacheflush.hasm/mips_mt.h
Detected Declarations
function maxvpesfunction maxtcsfunction rpsctl_setfunction nblsu_setfunction config7_setfunction set_itc_basefunction mips_mt_set_cpuoptionsfunction mips_mt_initmodule init mips_mt_init
Annotated Snippet
subsys_initcall(mips_mt_init);Annotation
- Immediate include surface: `linux/device.h`, `linux/kernel.h`, `linux/sched.h`, `linux/export.h`, `linux/interrupt.h`, `linux/security.h`, `asm/cpu.h`, `asm/processor.h`.
- Detected declarations: `function maxvpes`, `function maxtcs`, `function rpsctl_set`, `function nblsu_set`, `function config7_set`, `function set_itc_base`, `function mips_mt_set_cpuoptions`, `function mips_mt_init`, `module init mips_mt_init`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.