The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Lukas Wunner <lukas@wunner.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Crystal Wood <crwood@redhat.com>, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Clark Williams <clrkwllms@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Valentin Schneider <vschneid@redhat.com>,
	linux-kernel@vger.kernel.org,
	Attila Fazekas <afazekas@redhat.com>,
	linux-pci@vger.kernel.org, linux-rt-devel@lists.linux.dev,
	Bjorn Helgaas <helgaas@kernel.org>,
	Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
	Oliver OHalloran <oohall@gmail.com>
Subject: Re: [PATCH v2] genirq/manage: Reduce priority of forced secondary interrupt handler
Date: Tue, 28 Oct 2025 14:57:56 +0100	[thread overview]
Message-ID: <20251028135756.31PG0uHY@linutronix.de> (raw)
In-Reply-To: <aQDIxvU18vzB-1G-@wunner.de>

On 2025-10-28 14:44:38 [+0100], Lukas Wunner wrote:
> On Tue, Oct 28, 2025 at 01:06:52PM +0100, Sebastian Andrzej Siewior wrote:
> > On 2025-10-27 13:59:31 [+0100], Lukas Wunner wrote:
> > > The issue does not show on non-PREEMPT_RT because the primary handler
> > > runs in hardirq context and thus can preempt the threaded secondary
> > > handler, clear the Root Error Status register and prevent the secondary
> > > handler from getting stuck.
> > 
> > Not sure if I mentioned it before but this is due to forced threaded
> > IRQs which can also be enabled on non-PREEMPT_RT systems via `threadirqs`.
> 
> According to the commit which introduced the "threadirqs" command line
> option, 8d32a307e4fa ("genirq: Provide forced interrupt threading"),
> it is "mostly a debug option".  I guess the option allows testing
> the waters on arches which do not yet "select ARCH_SUPPORTS_RT"
> to see if force-threaded interrupts break anything.  I recall the
> option being available in mainline for much longer than PREEMPT_RT
> and it was definitely useful as a justification to upstream changes
> which were otherwise only needed by the out-of-tree PREEMPT_RT patches.

There are people using it without PREEMPT_RT due to $reasons. It is not
documented in Documentation/admin-guide/kernel-parameters.txt as an
option meant only for debugging.

> Intuitively I would assume that debug options are not worth calling out
> in commit messages or code comments as users and developers will
> primarily be interested in the real deal (i.e. PREEMPT_RT) and not
> an option which gets us only halfway there.  However if you
> (or anyone else) feels strongly about it, I'll be happy to respin.

I argued and sent patches to fix code which was wrong on PREEMPT_RT due
to threadirqs and was also wrong without PREEMPT_RT enabled but solely
with forced-threaded irqs.

But please wait once tglx/irq or peterz/sched says something here before
repining.

> Thanks for taking a look!
> 
> Lukas

Sebastian

  reply	other threads:[~2025-10-28 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 12:59 [PATCH v2] genirq/manage: Reduce priority of forced secondary interrupt handler Lukas Wunner
2025-10-28 12:06 ` Sebastian Andrzej Siewior
2025-10-28 13:44   ` Lukas Wunner
2025-10-28 13:57     ` Sebastian Andrzej Siewior [this message]
2025-11-01 20:35 ` [tip: irq/core] " tip-bot2 for Lukas Wunner

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=20251028135756.31PG0uHY@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=afazekas@redhat.com \
    --cc=bsegall@google.com \
    --cc=clrkwllms@kernel.org \
    --cc=crwood@redhat.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=helgaas@kernel.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=lukas@wunner.de \
    --cc=mahesh@linux.ibm.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=oohall@gmail.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    /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