tools/perf/util/perf-hooks.h
Source file repositories/reference/linux-study-clean/tools/perf/util/perf-hooks.h
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/util/perf-hooks.h- Extension
.h- Size
- 874 bytes
- Lines
- 41
- 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
perf-hooks-list.h
Detected Declarations
struct perf_hook_desc
Annotated Snippet
struct perf_hook_desc {
const char * const hook_name;
perf_hook_func_t * const p_hook_func;
void *hook_ctx;
};
extern void perf_hooks__invoke(const struct perf_hook_desc *);
extern void perf_hooks__recover(void);
#define PERF_HOOK(name) \
extern struct perf_hook_desc __perf_hook_desc_##name; \
static inline void perf_hooks__invoke_##name(void) \
{ \
perf_hooks__invoke(&__perf_hook_desc_##name); \
}
#include "perf-hooks-list.h"
#undef PERF_HOOK
extern int
perf_hooks__set_hook(const char *hook_name,
perf_hook_func_t hook_func,
void *hook_ctx);
extern perf_hook_func_t
perf_hooks__get_hook(const char *hook_name);
#ifdef __cplusplus
}
#endif
#endif
Annotation
- Immediate include surface: `perf-hooks-list.h`.
- Detected declarations: `struct perf_hook_desc`.
- 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.