From: Steven Rostedt <rostedt@goodmis.org>
To: Tomas Glozar <tglozar@redhat.com>
Cc: Crystal Wood <crwood@redhat.com>,
linux-trace-kernel@vger.kernel.org,
John Kacur <jkacur@redhat.com>,
Costa Shulyupin <costa.shul@redhat.com>
Subject: Re: [PATCH v2 0/7] tools/rtla: Code consolidation and osnoise actions
Date: Sat, 27 Sep 2025 05:47:41 -0400 [thread overview]
Message-ID: <20250927054741.10e22942@batman.local.home> (raw)
In-Reply-To: <20250927044454.0525d39c@batman.local.home>
On Sat, 27 Sep 2025 04:44:54 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> Normally, new code now would be a bit late for the merge window, but
> code in the tools directory isn't as strict. Thus, this is fine to push
> for the next merge window. I'll pull it in and send it to linux-next.
>
I applied the patches and then ran "make check" and triggered this:
tests/osnoise.t ... 13/17
not ok 13 - top stop at failed action
# Output match failed: "^abc"
# Output non-match failed: "defgh"
# Timer Latency
# 0 00:00:01 | IRQ Timer Latency (us) | Thread Timer Latency (us) | Ret user Timer Latency (us)
# CPU COUNT | cur min avg max | cur min avg max | cur min avg max
# 0 #1 | 3401 3401 3401 3401 | - - - - | - - - -
# 1 #1 | 2361 2361 2361 2361 | 2414 2414 2414 2414 | - - - -
# 2 #1 | 3079 3079 3079 3079 | - - - - | - - - -
# 3 #1 | 3538 3538 3538 3538 | 3586 3586 3586 3586 | - - - -
# 4 #1 | 3771 3771 3771 3771 | 3816 3816 3816 3816 | - - - -
# 5 #1 | 3487 3487 3487 3487 | 3536 3536 3536 3536 | - - - -
# 6 #1 | 3060 3060 3060 3060 | 3108 3108 3108 3108 | - - - -
# 7 #1 | 3677 3677 3677 3677 | 3723 3723 3723 3723 | - - - -
# ---------------|----------------------------------------|----------------------------------------|---------------------------------------
# defghALL #8 e0 | 2361 3296 3771 | 2414 3363 3816 | - - - | Timer Latency
# 0 00:00:02 | IRQ Timer Latency (us) | Thread Timer Latency (us) | Ret user Timer Latency (us)
# CPU COUNT | cur min avg max | cur min avg max | cur min avg max
# 0 #1 | 3401 3401 3401 3401 | - - - - | - - - -
# 1 #1 | 2361 2361 2361 2361 | 2414 2414 2414 2414 | - - - -
# 2 #1 | 3079 3079 3079 3079 | - - - - | - - - -
# 3 #1 | 3538 3538 3538 3538 | 3586 3586 3586 3586 | - - - -
# 4 #1 | 3771 3771 3771 3771 | 3816 3816 3816 3816 | - - - -
# 5 #1 | 3487 3487 3487 3487 | 3536 3536 3536 3536 | - - - -
# 6 #1 | 3060 3060 3060 3060 | 3108 3108 3108 3108 | - - - -
# 7 #1 | 3677 3677 3677 3677 | 3723 3723 3723 3723 | - - - -
# ---------------|----------------------------------------|----------------------------------------|---------------------------------------
# ALL #8 e0 | 2361 3296 3771 | 2414 3363 3816 | - - - |timerlat hit stop tracing
# ## CPU 1 hit stop tracing, analyzing it ##
# IRQ handler delay: (exit from idle) 2353.51 us (97.47 %)
# IRQ latency: 2361.99 us
# Timerlat IRQ duration: 29.36 us (1.22 %)
# Blocking thread: 8.87 us (0.37 %)
# swapper/1:0 8.87 us
# Softirq interference 9.90 us (0.41 %)
# SCHED:7 5.28 us
# RCU:9 4.62 us
# ------------------------------------------------------------------------
# Thread latency: 2414.68 us (100%)
# ## CPU 3 hit stop tracing, analyzing it ##
# IRQ handler delay: (exit from idle) 3528.33 us (98.39 %)
# IRQ latency: 3538.74 us
# Timerlat IRQ duration: 27.43 us (0.76 %)
# Blocking thread: 16.54 us (0.46 %)
# swapper/3:0 16.54 us
# ------------------------------------------------------------------------
# Thread latency: 3586.07 us (100%)
# ## CPU 4 hit stop tracing, analyzing it ##
# IRQ handler delay: (exit from idle) 3761.22 us (98.56 %)
# IRQ latency: 3771.21 us
# Timerlat IRQ duration: 25.32 us (0.66 %)
# Blocking thread: 16.38 us (0.43 %)
# swapper/4:0 16.38 us
# ------------------------------------------------------------------------
# Thread latency: 3816.32 us (100%)
# ## CPU 5 hit stop tracing, analyzing it ##
# IRQ handler delay: (exit from idle) 3475.39 us (98.28 %)
# IRQ latency: 3487.59 us
# Timerlat IRQ duration: 28.35 us (0.80 %)
# Blocking thread: 17.70 us (0.50 %)
# swapper/5:0 17.70 us
# ------------------------------------------------------------------------
# Thread latency: 3536.22 us (100%)
# ## CPU 6 hit stop tracing, analyzing it ##
# IRQ handler delay: (exit from idle) 3049.27 us (98.10 %)
# IRQ latency: 3060.32 us
# Timerlat IRQ duration: 27.52 us (0.89 %)
# Blocking thread: 17.06 us (0.55 %)
# swapper/6:0 17.06 us
# ------------------------------------------------------------------------
# Thread latency: 3108.31 us (100%)
# ## CPU 7 hit stop tracing, analyzing it ##
# IRQ handler delay: (exit from idle) 3667.57 us (98.49 %)
# IRQ latency: 3677.37 us
# Timerlat IRQ duration: 25.59 us (0.69 %)
# Blocking thread: 16.84 us (0.45 %)
# swapper/7:0 16.84 us
# ------------------------------------------------------------------------
# Thread latency: 3723.75 us (100%)
#
# Max timerlat IRQ latency from idle: 3771.21 us in cpu 4
#
# exit code 2
Is this expected?
-- Steve
next prev parent reply other threads:[~2025-09-27 9:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 2:23 [PATCH v2 0/7] tools/rtla: Code consolidation and osnoise actions Crystal Wood
2025-09-07 2:23 ` [PATCH v2 1/7] tools/rtla: Consolidate common parameters into shared structure Crystal Wood
2025-09-07 2:23 ` [PATCH v2 2/7] tools/rtla: Move top/hist params into common struct Crystal Wood
2025-09-07 2:23 ` [PATCH v2 3/7] tools/rtla: Create common_apply_config() Crystal Wood
2025-09-07 2:23 ` [PATCH v2 4/7] tools/rtla: Consolidate code between osnoise/timerlat and hist/top Crystal Wood
2025-09-07 19:51 ` Costa Shulyupin
2025-09-08 13:53 ` Costa Shulyupin
2025-09-07 2:23 ` [PATCH v2 5/7] tools/rtla: Fix -A option name in test comment Crystal Wood
2025-09-07 2:23 ` [PATCH v2 6/7] tools/rtla: Add test engine support for unexpected output Crystal Wood
2025-09-08 14:48 ` Crystal Wood
2025-09-07 2:23 ` [PATCH v2 7/7] tools/rtla: Add remaining support for osnoise actions Crystal Wood
2025-09-09 11:25 ` [PATCH v2 0/7] tools/rtla: Code consolidation and " Tomas Glozar
2025-09-26 14:19 ` Tomas Glozar
2025-09-27 8:44 ` Steven Rostedt
2025-09-27 9:47 ` Steven Rostedt [this message]
2025-09-27 10:09 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250927054741.10e22942@batman.local.home \
--to=rostedt@goodmis.org \
--cc=costa.shul@redhat.com \
--cc=crwood@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=tglozar@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox