From: Tomas Glozar Date: Thu, 23 Apr 2026 13:05:54 +0000 (+0200) Subject: rtla/tests: Extend timerlat top --aa-only coverage X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f78ba48f112113c89e37a914ccf52890fdd71006;p=thirdparty%2Fkernel%2Flinux.git rtla/tests: Extend timerlat top --aa-only coverage rtla-timerlat-top's --aa-only option is currently only tested for return value. Extend the tests to also check that only auto-analysis is being done via a negative match for the "Timer Latency" text in the top header, and further split the test case into two: - one test case for --aa-only stopping on threshold - one test case for --aa-only exiting without threshold being hit For both cases, the expected output ("analyzing it" or "Max latency was" respectively) is checked against in addition to the negative match. Reviewed-by: Wander Lairson Costa Link: https://lore.kernel.org/r/20260423130558.882022-6-tglozar@redhat.com Signed-off-by: Tomas Glozar --- diff --git a/tools/tracing/rtla/tests/timerlat.t b/tools/tracing/rtla/tests/timerlat.t index f47a82c115c7c..28c01d8b299d4 100644 --- a/tools/tracing/rtla/tests/timerlat.t +++ b/tools/tracing/rtla/tests/timerlat.t @@ -35,8 +35,10 @@ check_top_hist "set the automatic trace mode" \ "timerlat TOOL -a 5" 2 "analyzing it" check_top_hist "dump tasks" \ "timerlat TOOL -a 5 --dump-tasks" 2 "Printing CPU tasks" -check "print the auto-analysis if hits the stop tracing condition" \ - "timerlat top --aa-only 5" 2 +check "verify --aa-only stop on threshold" \ + "timerlat top --aa-only 5" 2 "analyzing it" "Timer Latency" +check "verify --aa-only max latency" \ + "timerlat top --aa-only 2000000 -d 1s" 0 "^ Max latency was" "Timer Latency" check_top_hist "disable auto-analysis" \ "timerlat TOOL -s 3 -T 10 -t --no-aa" 2 "" "analyzing it" check_top_q_hist "verify -c/--cpus" \