include/linux/unwind_user_types.h
Source file repositories/reference/linux-study-clean/include/linux/unwind_user_types.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/unwind_user_types.h- Extension
.h- Size
- 925 bytes
- Lines
- 47
- 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/types.h
Detected Declarations
struct unwind_stacktracestruct unwind_user_framestruct unwind_user_stateenum unwind_user_type_bitsenum unwind_user_type
Annotated Snippet
struct unwind_stacktrace {
unsigned int nr;
unsigned long *entries;
};
struct unwind_user_frame {
s32 cfa_off;
s32 ra_off;
s32 fp_off;
bool use_fp;
};
struct unwind_user_state {
unsigned long ip;
unsigned long sp;
unsigned long fp;
unsigned int ws;
enum unwind_user_type current_type;
unsigned int available_types;
bool topmost;
bool done;
};
#endif /* _LINUX_UNWIND_USER_TYPES_H */
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct unwind_stacktrace`, `struct unwind_user_frame`, `struct unwind_user_state`, `enum unwind_user_type_bits`, `enum unwind_user_type`.
- 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.