From: Andreas Ziegler <br015@umbiko.net>
To: Slade Watkins <srw@sladewatkins.net>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: rtla osnoise hist: average duration is always zero
Date: Mon, 26 Dec 2022 11:50:15 +0000 [thread overview]
Message-ID: <a900f403176c0e806051efc0f34f2912@umbiko.net> (raw)
In-Reply-To: <CA+pv=HO1mvnN5XZHkWDjWr=NJHJZxjcstiY4qtJGJ6mfsqPfQw@mail.gmail.com>
On 2022-12-24 21:17, Slade Watkins wrote:
> On Sat, Dec 24, 2022 at 7:48 AM Andreas Ziegler <br015@umbiko.net>
> wrote:
>>
>> -- Observed in, but not limited to, Linux 6.1.1
>
> Wait, "but not limited to"? What does that mean? Are there more
> versions affected?
This was meant to indicate that the bug is not a regression; it can be
found in every release since introduction in 5.17. Currently affected
are 6.1.y and 6.0.y kernel trees.
Regards,
Andreas
> -- Slade
next prev parent reply other threads:[~2022-12-26 11:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 12:39 Andreas Ziegler
2022-12-24 21:17 ` Slade Watkins
2022-12-26 11:50 ` Andreas Ziegler [this message]
2022-12-28 15:25 ` Daniel Bristot de Oliveira
2023-01-03 10:33 ` [PATCH 0/2 v2] rtla osnoise hist average calculation Andreas Ziegler
2023-01-03 10:33 ` [PATCH 1/2 v2] tools/tracing/rtla: osnoise_hist: use total duration for " Andreas Ziegler
2023-01-12 14:32 ` Daniel Bristot de Oliveira
2023-01-03 10:34 ` [PATCH 2/2 v2] tools/tracing/rtla: osnoise_hist: display average with two-digit precision Andreas Ziegler
2023-01-12 14:33 ` 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=a900f403176c0e806051efc0f34f2912@umbiko.net \
--to=br015@umbiko.net \
--cc=bristot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®