* Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x)
@ 2026-06-22 16:11 Luis Claudio R. Goncalves
2026-06-24 6:49 ` Sebastian Andrzej Siewior
0 siblings, 1 reply; 6+ messages in thread
From: Luis Claudio R. Goncalves @ 2026-06-22 16:11 UTC (permalink / raw)
To: Sebastian Andrzej Siewior, Steven Rostedt, Stable RT List
Hello!
The question is simple:
Should we have somebody maintaining the OOT RT patches for v12.x and v18.x,
the LTS versions that already have PREEMPT_RT in-tree?
As we still have a few OOT patches, after a while, people using PREEMPT_RT on
those versions may encounter conflicts trying to apply the old patches. And
as those patches are not in-tree, the fixes won't probably be routed via
Stable.
Best regards,
Luis
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x)
2026-06-22 16:11 Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x) Luis Claudio R. Goncalves
@ 2026-06-24 6:49 ` Sebastian Andrzej Siewior
2026-06-24 11:14 ` Luis Claudio R. Goncalves
0 siblings, 1 reply; 6+ messages in thread
From: Sebastian Andrzej Siewior @ 2026-06-24 6:49 UTC (permalink / raw)
To: Luis Claudio R. Goncalves; +Cc: Steven Rostedt, Stable RT List
On 2026-06-22 13:11:59 [-0300], Luis Claudio R. Goncalves wrote:
> Hello!
>
> The question is simple:
>
> Should we have somebody maintaining the OOT RT patches for v12.x and v18.x,
> the LTS versions that already have PREEMPT_RT in-tree?
>
> As we still have a few OOT patches, after a while, people using PREEMPT_RT on
> those versions may encounter conflicts trying to apply the old patches. And
> as those patches are not in-tree, the fixes won't probably be routed via
> Stable.
For 6.18, we have:
- 8250 console
- i915
- arm-32
- powerpc
For 6.12, we have additionally
- ktimers thread
- the whole lazy-preempt
So for v6.12 there are bits outstanding which can impact you.
For v6.18 if you are on arm64 then the mainline version is slightly
better than on x86 because on arm64 you might be using the pl011 UART
which has nbcon support since v6.15 while on x86 you almost always have
the 8250 which is not yet with nbcon support in-tree.
These are the missing bits. None of them are essential. If you on x86
and your kernel crashes, it is more likely to see a backtrace with nbcon
driver than without it.
> Best regards,
> Luis
Sebastian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x)
2026-06-24 6:49 ` Sebastian Andrzej Siewior
@ 2026-06-24 11:14 ` Luis Claudio R. Goncalves
2026-06-25 7:35 ` Alexander Dahl
2026-06-25 7:52 ` Sebastian Andrzej Siewior
0 siblings, 2 replies; 6+ messages in thread
From: Luis Claudio R. Goncalves @ 2026-06-24 11:14 UTC (permalink / raw)
To: Sebastian Andrzej Siewior; +Cc: Steven Rostedt, Stable RT List
On Wed, Jun 24, 2026 at 08:49:44AM +0200, Sebastian Andrzej Siewior wrote:
> On 2026-06-22 13:11:59 [-0300], Luis Claudio R. Goncalves wrote:
> > Hello!
> >
> > The question is simple:
> >
> > Should we have somebody maintaining the OOT RT patches for v12.x and v18.x,
> > the LTS versions that already have PREEMPT_RT in-tree?
> >
> > As we still have a few OOT patches, after a while, people using PREEMPT_RT on
> > those versions may encounter conflicts trying to apply the old patches. And
> > as those patches are not in-tree, the fixes won't probably be routed via
> > Stable.
>
> For 6.18, we have:
> - 8250 console
> - i915
> - arm-32
> - powerpc
>
> For 6.12, we have additionally
> - ktimers thread
> - the whole lazy-preempt
I need to correct myself here, our local hero Daniel Wagner is maintaining
the v6.12-rt version. Sorry for that :)
Sebastian, just to make sure I understood your answer, then we don't need
to keep the OOT patches up-to-date for v6.18-rt specifically? My question
came from comments raised on the last two RT maintainers meetings and the
LF RT Board meeting. I just want to have a good answer if somebody else
asks about that. And to volunteer if work is needed.
Best,
Luis
> So for v6.12 there are bits outstanding which can impact you.
> For v6.18 if you are on arm64 then the mainline version is slightly
> better than on x86 because on arm64 you might be using the pl011 UART
> which has nbcon support since v6.15 while on x86 you almost always have
> the 8250 which is not yet with nbcon support in-tree.
>
> These are the missing bits. None of them are essential. If you on x86
> and your kernel crashes, it is more likely to see a backtrace with nbcon
> driver than without it.
>
> > Best regards,
> > Luis
>
> Sebastian
>
---end quoted text---
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x)
2026-06-24 11:14 ` Luis Claudio R. Goncalves
@ 2026-06-25 7:35 ` Alexander Dahl
2026-06-25 8:02 ` Sebastian Andrzej Siewior
2026-06-25 7:52 ` Sebastian Andrzej Siewior
1 sibling, 1 reply; 6+ messages in thread
From: Alexander Dahl @ 2026-06-25 7:35 UTC (permalink / raw)
To: Luis Claudio R. Goncalves
Cc: Sebastian Andrzej Siewior, Steven Rostedt, Stable RT List
Hello,
just adding one datapoint here in case someone is wondering if there
are users out there? ;-)
Am Wed, Jun 24, 2026 at 08:14:51AM -0300 schrieb Luis Claudio R. Goncalves:
> I need to correct myself here, our local hero Daniel Wagner is maintaining
> the v6.12-rt version. Sorry for that :)
Good to know. Thank you for maintaing it for v6.12. :-)
> Sebastian, just to make sure I understood your answer, then we don't need
> to keep the OOT patches up-to-date for v6.18-rt specifically? My question
> came from comments raised on the last two RT maintainers meetings and the
> LF RT Board meeting. I just want to have a good answer if somebody else
> asks about that. And to volunteer if work is needed.
We still use v6.12 LTS with PREEMPT_RT on arm32 (at91),
and plan to use PREEMPT_RT on at91 (sam9x60, sama5d2) in the future.
If there are no regular patches for v6.18 we will probably skip that
and use the LTS coming later this year.
Greets
Alex
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x)
2026-06-25 7:35 ` Alexander Dahl
@ 2026-06-25 8:02 ` Sebastian Andrzej Siewior
0 siblings, 0 replies; 6+ messages in thread
From: Sebastian Andrzej Siewior @ 2026-06-25 8:02 UTC (permalink / raw)
To: Luis Claudio R. Goncalves, Steven Rostedt, Stable RT List
On 2026-06-25 09:35:19 [+0200], Alexander Dahl wrote:
> Hello,
>
> just adding one datapoint here in case someone is wondering if there
> are users out there? ;-)
Sure. Having an update from _any_ user feels good. At least the work is
used ;)
> > Sebastian, just to make sure I understood your answer, then we don't need
> > to keep the OOT patches up-to-date for v6.18-rt specifically? My question
> > came from comments raised on the last two RT maintainers meetings and the
> > LF RT Board meeting. I just want to have a good answer if somebody else
> > asks about that. And to volunteer if work is needed.
>
> We still use v6.12 LTS with PREEMPT_RT on arm32 (at91),
> and plan to use PREEMPT_RT on at91 (sam9x60, sama5d2) in the future.
>
> If there are no regular patches for v6.18 we will probably skip that
> and use the LTS coming later this year.
I did assume we have v6.18 in maintenance but somehow it skipped. *I*
usually skip updates if there are no clashes and nothing changes.
> Greets
> Alex
Sebastian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x)
2026-06-24 11:14 ` Luis Claudio R. Goncalves
2026-06-25 7:35 ` Alexander Dahl
@ 2026-06-25 7:52 ` Sebastian Andrzej Siewior
1 sibling, 0 replies; 6+ messages in thread
From: Sebastian Andrzej Siewior @ 2026-06-25 7:52 UTC (permalink / raw)
To: Luis Claudio R. Goncalves; +Cc: Steven Rostedt, Stable RT List
On 2026-06-24 08:14:51 [-0300], Luis Claudio R. Goncalves wrote:
> Sebastian, just to make sure I understood your answer, then we don't need
> to keep the OOT patches up-to-date for v6.18-rt specifically? My question
I did update v6.18 recently. I do think at the very least the 8250 bits
are important in case something goes wrong.
> came from comments raised on the last two RT maintainers meetings and the
> LF RT Board meeting. I just want to have a good answer if somebody else
> asks about that. And to volunteer if work is needed.
There isn't a lot that clashes in v6.12 and it is even less in v6.18.
However the printk/ serial changes in v6.18 caused some fallout exactly
there.
Hopefully we get the 8250 bits by the end of the year including i915 and
then we have just powerpc left and that one sysfs file and we can call
it a day.
> Best,
> Luis
Sebastian
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2026-06-25 8:02 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-06-22 16:11 Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x) Luis Claudio R. Goncalves
2026-06-24 6:49 ` Sebastian Andrzej Siewior
2026-06-24 11:14 ` Luis Claudio R. Goncalves
2026-06-25 7:35 ` Alexander Dahl
2026-06-25 8:02 ` Sebastian Andrzej Siewior
2026-06-25 7:52 ` Sebastian Andrzej Siewior
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox