tools/perf/tests/shell/stat_all_pfm.sh
Source file repositories/reference/linux-study-clean/tools/perf/tests/shell/stat_all_pfm.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/tests/shell/stat_all_pfm.sh- Extension
.sh- Size
- 1199 bytes
- Lines
- 52
- 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
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#!/bin/bash
# perf all libpfm4 events test
# SPDX-License-Identifier: GPL-2.0
if perf version --build-options | grep HAVE_LIBPFM | grep -q OFF
then
echo "Skipping, no libpfm4 support"
exit 2
fi
err=0
for p in $(perf list --raw-dump pfm)
do
if echo "$p" | grep -q unc_
then
echo "Skipping uncore event '$p' that may require additional options."
continue
fi
echo "Testing $p"
result=$(perf stat --pfm-events "$p" true 2>&1)
x=$?
if echo "$result" | grep -q "failed to parse event $p : invalid or missing unit mask"
then
continue
fi
if test "$x" -ne "0"
then
echo "Unexpected exit code '$x'"
err=1
fi
if ! echo "$result" | grep -q "$p" && ! echo "$result" | grep -q "<not supported>"
then
# We failed to see the event and it is supported. Possibly the workload was
# too small so retry with something longer.
result=$(perf stat --pfm-events "$p" perf bench internals synthesize 2>&1)
x=$?
if test "$x" -ne "0"
then
echo "Unexpected exit code '$x'"
err=1
fi
if ! echo "$result" | grep -q "$p"
then
echo "Event '$p' not printed in:"
echo "$result"
err=1
fi
fi
done
exit "$err"
Annotation
- 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.