arch/m68k/include/asm/pgalloc.h
Source file repositories/reference/linux-study-clean/arch/m68k/include/asm/pgalloc.h
File Facts
- System
- Linux kernel
- Corpus path
arch/m68k/include/asm/pgalloc.h- Extension
.h- Size
- 444 bytes
- Lines
- 23
- 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/mm.hlinux/highmem.hasm/setup.hasm/virtconvert.hasm/mcf_pgalloc.hasm/sun3_pgalloc.hasm/motorola_pgalloc.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef M68K_PGALLOC_H
#define M68K_PGALLOC_H
#include <linux/mm.h>
#include <linux/highmem.h>
#include <asm/setup.h>
#ifdef CONFIG_MMU
#include <asm/virtconvert.h>
#if defined(CONFIG_COLDFIRE)
#include <asm/mcf_pgalloc.h>
#elif defined(CONFIG_SUN3)
#include <asm/sun3_pgalloc.h>
#else
#include <asm/motorola_pgalloc.h>
#endif
extern void m68k_setup_node(int node);
#endif
#endif /* M68K_PGALLOC_H */
Annotation
- Immediate include surface: `linux/mm.h`, `linux/highmem.h`, `asm/setup.h`, `asm/virtconvert.h`, `asm/mcf_pgalloc.h`, `asm/sun3_pgalloc.h`, `asm/motorola_pgalloc.h`.
- 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.