tools/perf/util/values.h
Source file repositories/reference/linux-study-clean/tools/perf/util/values.h
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/util/values.h- Extension
.h- Size
- 676 bytes
- Lines
- 31
- 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
stdio.hlinux/types.h
Detected Declarations
struct evselstruct perf_read_values
Annotated Snippet
struct perf_read_values {
int threads;
int threads_max;
u32 *pid, *tid;
int num_counters;
int counters_max;
struct evsel **counters;
u64 **value;
};
int perf_read_values_init(struct perf_read_values *values);
void perf_read_values_destroy(struct perf_read_values *values);
int perf_read_values_add_value(struct perf_read_values *values,
u32 pid, u32 tid,
struct evsel *evsel, u64 value);
void perf_read_values_display(FILE *fp, struct perf_read_values *values,
int raw);
#endif /* __PERF_VALUES_H */
Annotation
- Immediate include surface: `stdio.h`, `linux/types.h`.
- Detected declarations: `struct evsel`, `struct perf_read_values`.
- 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.