arch/mips/mti-malta/malta-memory.c
Source file repositories/reference/linux-study-clean/arch/mips/mti-malta/malta-memory.c
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/mti-malta/malta-memory.c- Extension
.c- Size
- 1186 bytes
- Lines
- 45
- Domain
- Architecture Layer
- Bucket
- arch/mips
- Inferred role
- Architecture Layer: implementation source
- Status
- source 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.
Dependency Surface
linux/init.hlinux/memblock.hlinux/string.hasm/bootinfo.hasm/cdmm.hasm/maar.hasm/sections.hasm/fw/fw.h
Detected Declarations
function free_init_pages_eva_maltafunction fw_meminitfunction mips_cdmm_phys_base
Annotated Snippet
#include <linux/init.h>
#include <linux/memblock.h>
#include <linux/string.h>
#include <asm/bootinfo.h>
#include <asm/cdmm.h>
#include <asm/maar.h>
#include <asm/sections.h>
#include <asm/fw/fw.h>
/* determined physical memory size, not overridden by command line args */
unsigned long physical_memsize = 0L;
static void free_init_pages_eva_malta(void *begin, void *end)
{
free_init_pages("unused kernel", __pa_symbol((unsigned long *)begin),
__pa_symbol((unsigned long *)end));
}
void __init fw_meminit(void)
{
bool eva = IS_ENABLED(CONFIG_EVA);
free_init_pages_eva = eva ? free_init_pages_eva_malta : NULL;
}
phys_addr_t mips_cdmm_phys_base(void)
{
/* This address is "typically unused" */
return 0x1fc10000;
}
Annotation
- Immediate include surface: `linux/init.h`, `linux/memblock.h`, `linux/string.h`, `asm/bootinfo.h`, `asm/cdmm.h`, `asm/maar.h`, `asm/sections.h`, `asm/fw/fw.h`.
- Detected declarations: `function free_init_pages_eva_malta`, `function fw_meminit`, `function mips_cdmm_phys_base`.
- Atlas domain: Architecture Layer / arch/mips.
- Implementation status: source 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.