On Tue, 3 Apr 2018, Bjorn Helgaas wrote:
> [+cc Thomas, Rafael for real]
> On Tue, Apr 03, 2018 at 03:38:47PM -0500, Bjorn Helgaas wrote:
> > [+cc Thomas, Rafael]
> >
> > On Mon, Apr 02, 2018 at 10:21:58AM -0600, Keith Busch wrote:
> > > From: Oza Pawandeep <poza@xxxxxxxxxxxxxx>
> > >
> > > The DPC driver was acknowledging the DPC interrupt status in deferred
> > > work. That works for edge triggered interrupts, but causes an interrupt
> > > storm with level triggered legacy interrupts.
The problem is homebrewn in the driver. So, yes it needs to mask the
interrupt before returning from the irq handler if the rest of the magic is
done in a worker.
Though this could have been avoided if the driver simply would have used a
threaded interrupt. The core handles that correctly for any type of
interrupts, edge/level. The logic there is:
low_level_handler()
if (level)
irq_mask();
primary_handler();
wake_thread();
if (level && !thread_pending)
irq_unmask();
and the thread handler does
thread_handler()
thread_handler_function();
if (!thread_pending && masked && !disabled)
irq_unmask();
There is a reason why threaded interrupt handlers exist....
Thanks,
tglx
