tools/perf/tests/shell/base_report/test_basic.sh

File Facts

System

Linux kernel

Corpus path

tools/perf/tests/shell/base_report/test_basic.sh

Extension

.sh

Size

11089 bytes

Lines

286

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

", context_switch = 1, " < $LOGS_DIR/latency_header.log
CHECK_EXIT_CODE=$?

print_results $PERF_EXIT_CODE $CHECK_EXIT_CODE "latency header"
(( TEST_RESULT += $? ))


# The default report for latency profile should show Overhead and Latency fields (in that order).
$CMD_PERF report --stdio -i $CURRENT_TEST_DIR/perf.data.1 > $LOGS_DIR/latency_default.log 2> $LOGS_DIR/latency_default.err
PERF_EXIT_CODE=$?

"$DIR_PATH/../common/check_all_patterns_found.pl" \
	"# Overhead   Latency  Command" < $LOGS_DIR/latency_default.log
CHECK_EXIT_CODE=$?
"$DIR_PATH/../common/check_errors_whitelisted.pl" \
	"stderr-whitelist.txt" < $LOGS_DIR/latency_default.err
(( CHECK_EXIT_CODE += $? ))

print_results $PERF_EXIT_CODE $CHECK_EXIT_CODE "default report for latency profile"
(( TEST_RESULT += $? ))


# The latency report for latency profile should show Latency and Overhead fields (in that order).
$CMD_PERF report --latency --stdio -i $CURRENT_TEST_DIR/perf.data.1 > $LOGS_DIR/latency_latency.log 2> $LOGS_DIR/latency_latency.err
PERF_EXIT_CODE=$?

"$DIR_PATH/../common/check_all_patterns_found.pl" \
	"#  Latency  Overhead  Command" < $LOGS_DIR/latency_latency.log
CHECK_EXIT_CODE=$?
"$DIR_PATH/../common/check_errors_whitelisted.pl" \
	"stderr-whitelist.txt" < $LOGS_DIR/latency_latency.err
(( CHECK_EXIT_CODE += $? ))

print_results $PERF_EXIT_CODE $CHECK_EXIT_CODE "latency report for latency profile"
(( TEST_RESULT += $? ))


# Ensure parallelism histogram with parallelism filter does not fail/crash.
$CMD_PERF report --hierarchy --sort latency,parallelism,comm,symbol --parallelism=1,2 --stdio -i $CURRENT_TEST_DIR/perf.data.1 > $LOGS_DIR/parallelism_hierarchy.log 2> $LOGS_DIR/parallelism_hierarchy.err
PERF_EXIT_CODE=$?

"$DIR_PATH/../common/check_all_patterns_found.pl" \
	"#           Latency  Parallelism / Command / Symbol" \
	< $LOGS_DIR/parallelism_hierarchy.log
CHECK_EXIT_CODE=$?
"$DIR_PATH/../common/check_errors_whitelisted.pl" \
	"stderr-whitelist.txt" < $LOGS_DIR/parallelism_hierarchy.err
(( CHECK_EXIT_CODE += $? ))

print_results $PERF_EXIT_CODE $CHECK_EXIT_CODE "parallelism histogram"
(( TEST_RESULT += $? ))


# TODO: $CMD_PERF report -n --showcpuutilization -TUxDg 2> 01.log

# print overall results
print_overall_results "$TEST_RESULT"
exit $?

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.