tools/perf/util/pmu.l
Source file repositories/reference/linux-study-clean/tools/perf/util/pmu.l
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/util/pmu.l- Extension
.l- Size
- 767 bytes
- Lines
- 49
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: tools
- Status
- atlas-only
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.
Dependency Surface
stdlib.hlinux/bitops.hpmu.hpmu-bison.h
Detected Declarations
function valuefunction perf_pmu_wrap
Annotated Snippet
%option prefix="perf_pmu_"
%option reentrant
%option bison-bridge
%{
#include <stdlib.h>
#include <linux/bitops.h>
#include "pmu.h"
#include "pmu-bison.h"
char *perf_pmu_get_text(yyscan_t yyscanner);
YYSTYPE *perf_pmu_get_lval(yyscan_t yyscanner);
static int value(yyscan_t scanner, int base)
{
YYSTYPE *yylval = perf_pmu_get_lval(scanner);
char *text = perf_pmu_get_text(scanner);
long num;
errno = 0;
num = strtoul(text, NULL, base);
if (errno)
return PP_ERROR;
yylval->num = num;
return PP_VALUE;
}
%}
num_dec [0-9]+
%%
{num_dec} { return value(yyscanner, 10); }
config { return PP_CONFIG; }
- { return '-'; }
: { return ':'; }
, { return ','; }
. { ; }
\n { ; }
%%
int perf_pmu_wrap(void *scanner __maybe_unused)
{
return 1;
}
Annotation
- Immediate include surface: `stdlib.h`, `linux/bitops.h`, `pmu.h`, `pmu-bison.h`.
- Detected declarations: `function value`, `function perf_pmu_wrap`.
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: atlas-only.
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.