arch/m68k/include/asm/virtconvert.h
Source file repositories/reference/linux-study-clean/arch/m68k/include/asm/virtconvert.h
File Facts
- System
- Linux kernel
- Corpus path
arch/m68k/include/asm/virtconvert.h- Extension
.h- Size
- 815 bytes
- Lines
- 41
- Domain
- Architecture Layer
- Bucket
- arch/m68k
- 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/compiler.hlinux/mmzone.hasm/setup.hasm/page.h
Detected Declarations
function virt_to_phys
Annotated Snippet
#ifndef __VIRT_CONVERT__
#define __VIRT_CONVERT__
/*
* Macros used for converting between virtual and physical mappings.
*/
#ifdef __KERNEL__
#include <linux/compiler.h>
#include <linux/mmzone.h>
#include <asm/setup.h>
#include <asm/page.h>
/*
* Change virtual addresses to physical addresses and vv.
*/
#define virt_to_phys virt_to_phys
static inline unsigned long virt_to_phys(void *address)
{
return __pa(address);
}
#define phys_to_virt phys_to_virt
static inline void *phys_to_virt(unsigned long address)
{
return __va(address);
}
/*
* IO bus memory addresses are 1:1 with the physical address,
* deprecated globally but still used on two machines.
*/
#if defined(CONFIG_AMIGA) || defined(CONFIG_VME)
#define virt_to_bus virt_to_phys
#endif
#endif
#endif
Annotation
- Immediate include surface: `linux/compiler.h`, `linux/mmzone.h`, `asm/setup.h`, `asm/page.h`.
- Detected declarations: `function virt_to_phys`.
- Atlas domain: Architecture Layer / arch/m68k.
- 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.