[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210318085148.3gnvlvzukqsmo2p2@linutronix.de>
Date: Thu, 18 Mar 2021 09:51:48 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Johan Hovold <johan@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>,
netdev <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-serial@...r.kernel.org
Subject: Re: [patch 1/1] genirq: Disable interrupts for force threaded
handlers
On 2021-03-17 17:23:39 [+0100], Johan Hovold wrote:
> > > thread(irq_A)
> > > irq_handler(A)
> > > spin_lock(&foo->lock);
> > >
> > > interrupt(irq_B)
> > > irq_handler(B)
> > > spin_lock(&foo->lock);
> >
> > It will not because both threads will wake_up(thread).
>
> Note that the above says "interrupt(irq_B)" suggesting it's a
> non-threaded interrupt unlike irq_A.
I missed that bit, thanks.
Sebastian
Powered by blists - more mailing lists