arch/arm64/mm/physaddr.c
Source file repositories/reference/linux-study-clean/arch/arm64/mm/physaddr.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/mm/physaddr.c- Extension
.c- Size
- 785 bytes
- Lines
- 32
- 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/bug.hlinux/export.hlinux/types.hlinux/mmdebug.hlinux/mm.hasm/memory.h
Detected Declarations
function __virt_to_physfunction __phys_addr_symbolexport __virt_to_physexport __phys_addr_symbol
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#include <linux/bug.h>
#include <linux/export.h>
#include <linux/types.h>
#include <linux/mmdebug.h>
#include <linux/mm.h>
#include <asm/memory.h>
phys_addr_t __virt_to_phys(unsigned long x)
{
WARN(!__is_lm_address(__tag_reset(x)),
"virt_to_phys used for non-linear address: %p (%pS)\n",
(void *)x,
(void *)x);
return __virt_to_phys_nodebug(x);
}
EXPORT_SYMBOL(__virt_to_phys);
phys_addr_t __phys_addr_symbol(unsigned long x)
{
/*
* This is bounds checking against the kernel image only.
* __pa_symbol should only be used on kernel symbol addresses.
*/
VIRTUAL_BUG_ON(x < (unsigned long) KERNEL_START ||
x > (unsigned long) KERNEL_END);
return __pa_symbol_nodebug(x);
}
EXPORT_SYMBOL(__phys_addr_symbol);
Annotation
- Immediate include surface: `linux/bug.h`, `linux/export.h`, `linux/types.h`, `linux/mmdebug.h`, `linux/mm.h`, `asm/memory.h`.
- Detected declarations: `function __virt_to_phys`, `function __phys_addr_symbol`, `export __virt_to_phys`, `export __phys_addr_symbol`.
- 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.