tools/testing/memblock/linux/mmzone.h
Source file repositories/reference/linux-study-clean/tools/testing/memblock/linux/mmzone.h
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/memblock/linux/mmzone.h- Extension
.h- Size
- 949 bytes
- Lines
- 43
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: implementation source
- Status
- source implementation candidate
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/atomic.hlinux/memory_hotplug.h
Detected Declarations
struct zoneenum zone_typeenum migratetype
Annotated Snippet
struct zone {
atomic_long_t managed_pages;
};
typedef struct pglist_data {
struct zone node_zones[MAX_NR_ZONES];
} pg_data_t;
enum migratetype {
MIGRATE_CMA,
};
#endif
Annotation
- Immediate include surface: `linux/atomic.h`, `linux/memory_hotplug.h`.
- Detected declarations: `struct zone`, `enum zone_type`, `enum migratetype`.
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: source implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
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.