include/linux/pstore_ram.h
Source file repositories/reference/linux-study-clean/include/linux/pstore_ram.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/pstore_ram.h- Extension
.h- Size
- 883 bytes
- Lines
- 43
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/pstore.h
Detected Declarations
struct persistent_ram_ecc_infostruct ramoops_platform_data
Annotated Snippet
struct persistent_ram_ecc_info {
int block_size;
int ecc_size;
int symsize;
int poly;
uint16_t *par;
};
/*
* Ramoops platform data
* @mem_size memory size for ramoops
* @mem_address physical memory address to contain ramoops
*/
#define RAMOOPS_FLAG_FTRACE_PER_CPU BIT(0)
struct ramoops_platform_data {
unsigned long mem_size;
phys_addr_t mem_address;
unsigned int mem_type;
unsigned long record_size;
unsigned long console_size;
unsigned long ftrace_size;
unsigned long pmsg_size;
int max_reason;
u32 flags;
struct persistent_ram_ecc_info ecc_info;
};
#endif
Annotation
- Immediate include surface: `linux/pstore.h`.
- Detected declarations: `struct persistent_ram_ecc_info`, `struct ramoops_platform_data`.
- 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.