tools/perf/util/pfm.h
Source file repositories/reference/linux-study-clean/tools/perf/util/pfm.h
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/util/pfm.h- Extension
.h- Size
- 795 bytes
- Lines
- 39
- 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
print-events.hsubcmd/parse-options.hlinux/compiler.h
Detected Declarations
function parse_libpfm_events_optionfunction print_libpfm_events
Annotated Snippet
#ifndef __PERF_PFM_H
#define __PERF_PFM_H
#include "print-events.h"
#include <subcmd/parse-options.h>
#ifdef HAVE_LIBPFM
int parse_libpfm_events_option(const struct option *opt, const char *str,
int unset);
void print_libpfm_events(const struct print_callbacks *print_cb, void *print_state);
#else
#include <linux/compiler.h>
static inline int parse_libpfm_events_option(
const struct option *opt __maybe_unused,
const char *str __maybe_unused,
int unset __maybe_unused)
{
return 0;
}
static inline void print_libpfm_events(const struct print_callbacks *print_cb __maybe_unused,
void *print_state __maybe_unused)
{
}
#endif
#endif /* __PERF_PFM_H */
Annotation
- Immediate include surface: `print-events.h`, `subcmd/parse-options.h`, `linux/compiler.h`.
- Detected declarations: `function parse_libpfm_events_option`, `function print_libpfm_events`.
- 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.