tools/perf/util/map_symbol.h
Source file repositories/reference/linux-study-clean/tools/perf/util/map_symbol.h
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/util/map_symbol.h- Extension
.h- Size
- 713 bytes
- Lines
- 34
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/types.h
Detected Declarations
struct threadstruct mapsstruct mapstruct symbolstruct map_symbolstruct addr_map_symbol
Annotated Snippet
struct map_symbol {
struct thread *thread;
struct map *map;
struct symbol *sym;
};
struct addr_map_symbol {
struct map_symbol ms;
u64 addr;
u64 al_addr;
char al_level;
u64 phys_addr;
u64 data_page_size;
};
void map_symbol__exit(struct map_symbol *ms);
void addr_map_symbol__exit(struct addr_map_symbol *ams);
void map_symbol__copy(struct map_symbol *dst, struct map_symbol *src);
void addr_map_symbol__copy(struct addr_map_symbol *dst, struct addr_map_symbol *src);
#endif // __PERF_MAP_SYMBOL
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct thread`, `struct maps`, `struct map`, `struct symbol`, `struct map_symbol`, `struct addr_map_symbol`.
- Atlas domain: Support Tooling And Documentation / tools.
- 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.