include/linux/kho/abi/memblock.h
Source file repositories/reference/linux-study-clean/include/linux/kho/abi/memblock.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/kho/abi/memblock.h- Extension
.h- Size
- 2204 bytes
- Lines
- 74
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _LINUX_KHO_ABI_MEMBLOCK_H
#define _LINUX_KHO_ABI_MEMBLOCK_H
/**
* DOC: memblock kexec handover ABI
*
* Memblock can serialize its current memory reservations created with
* reserve_mem command line option across kexec through KHO.
* The post-KHO kernel can then consume these reservations and they are
* guaranteed to have the same physical address.
*
* The state is serialized using Flattened Device Tree (FDT) format. Any
* modification to the FDT structure, node properties, or the compatible
* strings constitutes a breaking change. Such changes require incrementing the
* version number in the relevant `_COMPATIBLE` string to prevent a new kernel
* from misinterpreting data from an old kernel.
*
* Changes are allowed provided the compatibility version is incremented.
* However, backward/forward compatibility is only guaranteed for kernels
* supporting the same ABI version.
*
* FDT Structure Overview:
* The entire memblock state is encapsulated within a single KHO entry named
* "memblock".
* This entry contains an FDT with the following layout:
*
* .. code-block:: none
*
* / {
* compatible = "memblock-v1";
*
* n1 {
* compatible = "reserve-mem-v1";
* start = <0xc06b 0x4000000>;
* size = <0x04 0x00>;
* };
* };
*
* Main memblock node (/):
*
* - compatible: "memblock-v1"
* Identifies the overall memblock ABI version.
*
* reserved_mem node:
* These nodes describe all reserve_mem regions. The node name is the name
* defined by the user for a reserve_mem region.
*
* - compatible: "reserve-mem-v1"
*
* Identifies the ABI version of reserve_mem descriptions
*
* - start: u64
*
* Physical address of the reserved memory region.
*
* - size: u64
*
* size in bytes of the reserved memory region.
*/
/* Top level memblock FDT node name. */
#define MEMBLOCK_KHO_FDT "memblock"
/* The compatible string for the memblock FDT root node. */
#define MEMBLOCK_KHO_NODE_COMPATIBLE "memblock-v1"
/* The compatible string for the reserve_mem FDT nodes. */
#define RESERVE_MEM_KHO_NODE_COMPATIBLE "reserve-mem-v1"
#endif /* _LINUX_KHO_ABI_MEMBLOCK_H */
Annotation
- Atlas domain: Core OS / Core Kernel Interface.
- 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.