From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: linux-kernel@vger.kernel.org, linux-trace-devel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Cc: William White <chwhite@redhat.com>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: [PATCH 0/3] rtla fixes for 6.5
Date: Fri, 4 Aug 2023 17:52:10 +0200 [thread overview]
Message-ID: <cover.1691162043.git.bristot@kernel.org> (raw)
Here are some fixes for rtla timerlat auto-analysis.
The first one zeroes the variable that accounts for the amount of
thread interference when a new cycle begins.
The second fixes an imprecision on the IRQ delay account when
the value is near 0.
The last one fixes the case when an IRQ interference for the
next activation is considered for the previous one.
Daniel Bristot de Oliveira (3):
rtla/timerlat_aa: Zero thread sum after every sample analysis
rtla/timerlat_aa: Fix negative irq delay
rtla/timerlat_aa: Fix previous IRQ delay for IRQs that happens after
thread sample
tools/tracing/rtla/src/timerlat_aa.c | 32 ++++++++++++++++++++++------
1 file changed, 26 insertions(+), 6 deletions(-)
--
2.38.1
next reply other threads:[~2023-08-04 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 15:52 Daniel Bristot de Oliveira [this message]
2023-08-04 15:52 ` [PATCH 1/3] rtla/timerlat_aa: Zero thread sum after every sample analysis Daniel Bristot de Oliveira
2023-08-04 15:52 ` [PATCH 2/3] rtla/timerlat_aa: Fix negative IRQ delay Daniel Bristot de Oliveira
2023-08-04 15:52 ` [PATCH 3/3] rtla/timerlat_aa: Fix previous IRQ delay for IRQs that happens after thread sample Daniel Bristot de Oliveira
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=cover.1691162043.git.bristot@kernel.org \
--to=bristot@kernel.org \
--cc=chwhite@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).