All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Gustavo Padovan <gus@collabora.com>
Cc: kernelci <kernelci@lists.linux.dev>,
	linux-rt-devel <linux-rt-devel@lists.linux.dev>,
	stable-rt <stable-rt@vger.kernel.org>,
	Daniel Wagner <wagi@monom.org>
Subject: Re: PREEMPT_RT testing on kernelci
Date: Tue, 11 Feb 2025 16:20:18 +0100	[thread overview]
Message-ID: <20250211152018.sK91dh93@linutronix.de> (raw)
In-Reply-To: <194f4c989de.bdd18d3279996.2067896388251039576@collabora.com>

On 2025-02-11 08:33:56 [-0300], Gustavo Padovan wrote:
> Hi Sebastian,
Hi Gustavo,

> Thank you for your email. We are happy that KernelCI is helping you with tests.
;)
>  > Since PREEMPT_RT is now available upstream, would it work to compile and 
>  > enable some of its tests for the supported architectures on Linus' tree 
>  > and maybe the -next tree? I don't think that happens at the moment, I 
>  > saw only a few stable-rt trees. 
> 
> https://github.com/kernelci/kernelci-pipeline/pull/1010
> 
> This will get it enabled for mainline and next. Allow us a few days for processing and
> deploying this in production.

Sure. Just poke if you have something to inspect or look at because of
$reason.

The architectures, that support RT are what you see in
| git grep ARCH_SUPPORTS_RT arch/

so this does not include arm at current stage for instance. So in
general, if you can't select CONFIG_PREEMPT_RT you can skip the
config/ build/ test.

RiscV on the other hand is supported.

> Beyond that, we would love any feedback you have to us. A lot of the infra
> we have today is new, so there are still rough edges to work on.

Sure. How do I see easily what is tested/ done? I could maybe wait a few
days and check the dashboard. The link from above showed timerlat has
been but I didn't manage to figure what has been. I guess there is a
script somewhere handling the logic.

> Best,
> 
> - Gus

Sebastian

  reply	other threads:[~2025-02-11 15:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11  9:05 PREEMPT_RT testing on kernelci Sebastian Andrzej Siewior
2025-02-11 11:33 ` Gustavo Padovan
2025-02-11 15:20   ` Sebastian Andrzej Siewior [this message]
2025-02-11 15:50     ` Gustavo Padovan
2025-02-11 16:26       ` Mark Brown
2025-02-13  8:52       ` Sebastian Andrzej Siewior
2025-04-11 19:44         ` Sebastian Andrzej Siewior
2025-04-14 15:14           ` Gustavo Padovan
2025-04-17 10:04             ` Sebastian Andrzej Siewior
2025-04-17 13:10               ` Gustavo Padovan
2025-04-17 15:11                 ` Sebastian Andrzej Siewior
2025-04-18 15:05                   ` Gustavo Padovan
2025-02-11 15:33 ` Guenter Roeck
2025-02-11 15:37   ` Sebastian Andrzej Siewior
2025-02-11 15:49     ` Guenter Roeck
2025-02-12 17:17   ` Donald Zickus
2025-02-12 17:59     ` Guenter Roeck

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=20250211152018.sK91dh93@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=gus@collabora.com \
    --cc=kernelci@lists.linux.dev \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=stable-rt@vger.kernel.org \
    --cc=wagi@monom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.