From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Denys Fedoryshchenko <denys.f@collabora.com>
Cc: kernelci <kernelci@lists.linux.dev>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: Debugging PREEMPT_RT spikes on kernelci
Date: Thu, 19 Nov 2026 09:09:10 +0100 [thread overview]
Message-ID: <20261119080910.RIjU3Vyp@linutronix.de> (raw)
In-Reply-To: <1a1e41d96b1.3e56ef281896928.385630952830763087@collabora.com>
On 2026-11-16 13:28:26 [+0200], Denys Fedoryshchenko wrote:
> Hello,
Hi,
> I will do deploy production right now.
Thank you.
> Usually changes are deployed weekly, unless there is breaking changes
> that might need more needing.
I see. Thank you for the information.
Judging from yesterday's run
https://dashboard.kernelci.org/test/maestro%3A6afe07fc99c74e1a99855381
the config bits are merged and cyclictest reports
| T: 0 ( 484) P:98 I:1000 C: 540000 Min: 4 Act: 4 Avg: 13 Max: 98
| T: 1 ( 491) P:98 I:1500 C: 360000 Min: 4 Act: 7 Avg: 14 Max: 92
which looks good.
Sebastian
prev parent reply other threads:[~2026-11-19 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 11:11 Debugging PREEMPT_RT spikes on kernelci Sebastian Andrzej Siewior
2026-11-16 11:28 ` Denys Fedoryshchenko
2026-11-19 8:09 ` Sebastian Andrzej Siewior [this message]
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=20261119080910.RIjU3Vyp@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=denys.f@collabora.com \
--cc=john.ogness@linutronix.de \
--cc=kernelci@lists.linux.dev \
/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 NNTP newsgroup(s).