tools/perf/tests/shell/list.sh
Source file repositories/reference/linux-study-clean/tools/perf/tests/shell/list.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/tests/shell/list.sh- Extension
.sh- Size
- 758 bytes
- Lines
- 38
- 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_list_json
Annotated Snippet
#!/bin/bash
# perf list tests
# SPDX-License-Identifier: GPL-2.0
set -e
shelldir=$(dirname "$0")
# shellcheck source=lib/setup_python.sh
. "${shelldir}"/lib/setup_python.sh
list_output=$(mktemp /tmp/__perf_test.list_output.json.XXXXX)
cleanup() {
rm -f "${list_output}"
trap - EXIT TERM INT
}
trap_cleanup() {
cleanup
exit 1
}
trap trap_cleanup EXIT TERM INT
test_list_json() {
echo "Json output test"
# Generate perf list json output into list_output file.
perf list -j -o "${list_output}"
# Validate the json using python, redirect the json copy to /dev/null as
# otherwise the test may block writing to stdout.
$PYTHON -m json.tool "${list_output}" /dev/null
echo "Json output test [Success]"
}
test_list_json
cleanup
exit 0
Annotation
- Detected declarations: `function test_list_json`.
- 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.