arch/arm64/mm/ioremap.c
Source file repositories/reference/linux-study-clean/arch/arm64/mm/ioremap.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/mm/ioremap.c- Extension
.c- Size
- 1284 bytes
- Lines
- 59
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- 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.
Dependency Surface
linux/mm.hlinux/io.h
Detected Declarations
function arm64_ioremap_prot_hook_registerfunction registeredfunction early_ioremap_initfunction arch_memremap_can_ram_remapexport __ioremap_prot
Annotated Snippet
WARN_ON(ioremap_prot_hook(phys_addr, size, &pgprot))) {
return NULL;
}
return generic_ioremap_prot(phys_addr, size, pgprot);
}
EXPORT_SYMBOL(__ioremap_prot);
/*
* Must be called after early_fixmap_init
*/
void __init early_ioremap_init(void)
{
early_ioremap_setup();
}
bool arch_memremap_can_ram_remap(resource_size_t offset, size_t size,
unsigned long flags)
{
unsigned long pfn = PHYS_PFN(offset);
return pfn_is_map_memory(pfn);
}
Annotation
- Immediate include surface: `linux/mm.h`, `linux/io.h`.
- Detected declarations: `function arm64_ioremap_prot_hook_register`, `function registered`, `function early_ioremap_init`, `function arch_memremap_can_ram_remap`, `export __ioremap_prot`.
- Atlas domain: Architecture Layer / arch/arm64.
- 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.