From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
stable-rt <stable-rt@vger.kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Davidlohr Bueso <dave@stgolabs.net>,
Frederic Weisbecker <frederic@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Thomas Gleixner <tglx@linutronix.de>,
Florian Bezdeka <florian.bezdeka@siemens.com>,
Pavel Machek <pavel@denx.de>
Subject: Re: [PATCH v3 3/3] softirq: Use a dedicated thread for timer wakeups on PREEMPT_RT.
Date: Tue, 2 Dec 2025 14:22:12 +0100 [thread overview]
Message-ID: <20251202132212.uxWTkFJd@linutronix.de> (raw)
In-Reply-To: <afbd1a03-0458-4c06-a96a-2d5f34e2632e@siemens.com>
On 2025-12-02 13:39:56 [+0100], Jan Kiszka wrote:
> On 02.12.25 09:24, Sebastian Andrzej Siewior wrote:
> > On 2025-12-01 22:51:50 [+0100], Jan Kiszka wrote:
> >> How should we handle this? Consider 6.12 mainline with -rt and cgroups
> >> as potentially broken, asking people to user 6.12-rt? Or port this back?
> >
> > If you have everything in v6.12 for an useable RT system and this is the
> > only missing piece I could ask the stable nicely to backport this.
> >
>
> Given that this is a fix for potential lock-up... Does it have
> dependencies? The other two patches in this series are optimizations
> only, or should they better join the backport?
Just an optimisation if I am not mistaken but it will conflict if not
backported.
> Jan
Sebastian
prev parent reply other threads:[~2025-12-02 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 14:51 PATCH v3 0/3] softirq: Use a dedicated thread for timer wakeups with forced-threading Sebastian Andrzej Siewior
2024-11-06 14:51 ` [PATCH v3 1/3] hrtimer: Use __raise_softirq_irqoff() to raise the softirq Sebastian Andrzej Siewior
2024-11-06 14:51 ` [PATCH v3 2/3] timers: " Sebastian Andrzej Siewior
2024-11-06 14:51 ` [PATCH v3 3/3] softirq: Use a dedicated thread for timer wakeups on PREEMPT_RT Sebastian Andrzej Siewior
2025-12-01 21:51 ` Jan Kiszka
2025-12-01 23:49 ` Luis Claudio R. Goncalves
2025-12-02 6:57 ` Jan Kiszka
2025-12-02 8:22 ` Sebastian Andrzej Siewior
2025-12-02 8:24 ` Sebastian Andrzej Siewior
2025-12-02 12:39 ` Jan Kiszka
2025-12-02 13:22 ` 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=20251202132212.uxWTkFJd@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=dave@stgolabs.net \
--cc=florian.bezdeka@siemens.com \
--cc=frederic@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=pavel@denx.de \
--cc=rcu@vger.kernel.org \
--cc=stable-rt@vger.kernel.org \
--cc=tglx@linutronix.de \
/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