From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
Mike Schanne <mschanne@kns.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-rt-devel@lists.linux.dev" <linux-rt-devel@lists.linux.dev>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Todd Leitzel <tleitzel@kns.com>
Subject: Re: [PATCH] uio: eliminate extraneous irq thread under CONFIG_PREEMPT_RT
Date: Tue, 25 Aug 2026 14:44:53 +0200 [thread overview]
Message-ID: <20260825124453.INbPSgYf@linutronix.de> (raw)
In-Reply-To: <20260820141222.gPkfKLpT@linutronix.de>
On 2026-08-20 16:12:22 [+0200], To Chris Packham wrote:
>
> If so, you realize that uio_interrupt_handler() isn't called at all?
Mike could you please post a patch which reverts f8a27dfa4b82d ("uio:
use threaded interrupts") because
- it breaks the threadirqs case including PREEMPT_RT
- I doubt that it solved the reported problem because it does not invoke
the primary handler of UIO at all because it gets overwritten to
irq_nested_primary_handler().
As for the Chris case, I would suggest to check the IRQ for
irq_settings_is_nested_thread() and then use request_threaded_irq().
Sebastian
next prev parent reply other threads:[~2026-08-25 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TY0PR0101MB48672132B8525B7B39565EE4D2A52@TY0PR0101MB4867.apcprd01.prod.exchangelabs.com>
2026-08-19 15:06 ` [PATCH] uio: eliminate extraneous irq thread under CONFIG_PREEMPT_RT Sebastian Andrzej Siewior
2026-08-19 20:48 ` Chris Packham
2026-08-20 14:12 ` Sebastian Andrzej Siewior
2026-08-25 12:44 ` Sebastian Andrzej Siewior [this message]
2026-08-19 15:06 Mike Schanne
2026-08-25 10:45 ` Ahmed S. Darwish
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=20260825124453.INbPSgYf@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-rt-users@vger.kernel.org \
--cc=mschanne@kns.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tleitzel@kns.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