tools/perf/tests/shell/perf-report-hierarchy.sh
Source file repositories/reference/linux-study-clean/tools/perf/tests/shell/perf-report-hierarchy.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/tests/shell/perf-report-hierarchy.sh- Extension
.sh- Size
- 763 bytes
- Lines
- 44
- 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
function test_report_hierarchy
Annotated Snippet
#!/bin/bash
# perf report --hierarchy
# SPDX-License-Identifier: GPL-2.0
# Arnaldo Carvalho de Melo <acme@redhat.com>
set -e
temp_dir=$(mktemp -d /tmp/perf-test-report.XXXXXXXXXX)
cleanup()
{
trap - EXIT TERM INT
sane=$(echo "${temp_dir}" | cut -b 1-21)
if [ "${sane}" = "/tmp/perf-test-report" ] ; then
echo "--- Cleaning up ---"
rm -rf "${temp_dir:?}/"*
rmdir "${temp_dir}"
fi
}
trap_cleanup()
{
cleanup
exit 1
}
trap trap_cleanup EXIT TERM INT
test_report_hierarchy()
{
echo "perf report --hierarchy"
perf_data="${temp_dir}/perf-report-hierarchy-perf.data"
perf record -o "${perf_data}" uname
perf report --hierarchy -i "${perf_data}" > /dev/null
echo "perf report --hierarchy test [Success]"
}
test_report_hierarchy
cleanup
exit 0
Annotation
- Detected declarations: `function test_report_hierarchy`.
- 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.