tools/perf/util/tp_pmu.h
Source file repositories/reference/linux-study-clean/tools/perf/util/tp_pmu.h
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/util/tp_pmu.h- Extension
.h- Size
- 754 bytes
- Lines
- 20
- 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
pmu.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __TP_PMU_H
#define __TP_PMU_H
#include "pmu.h"
typedef int (*tp_sys_callback)(void *state, const char *sys_name);
typedef int (*tp_event_callback)(void *state, const char *sys_name, const char *evt_name);
int tp_pmu__id(const char *sys, const char *name);
int tp_pmu__for_each_tp_event(const char *sys, void *state, tp_event_callback cb);
int tp_pmu__for_each_tp_sys(void *state, tp_sys_callback cb);
bool perf_pmu__is_tracepoint(const struct perf_pmu *pmu);
int tp_pmu__for_each_event(struct perf_pmu *pmu, void *state, pmu_event_callback cb);
size_t tp_pmu__num_events(struct perf_pmu *pmu);
bool tp_pmu__have_event(struct perf_pmu *pmu, const char *name);
#endif /* __TP_PMU_H */
Annotation
- Immediate include surface: `pmu.h`.
- 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.