[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zfvwai62.ffs@tglx>
Date: Mon, 19 Feb 2024 10:59:33 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Leonardo Bras <leobras@...hat.com>, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>, Jiri Slaby <jirislaby@...nel.org>, Tony
Lindgren <tony@...mide.com>, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com>, John Ogness
<john.ogness@...utronix.de>, Ilpo Järvinen
<ilpo.jarvinen@...ux.intel.com>, Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>, Leonardo Bras <leobras@...hat.com>,
Florian Fainelli <florian.fainelli@...adcom.com>, Shanker Donthineni
<sdonthineni@...dia.com>
Cc: linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [RFC PATCH v2 3/4] irq: Introduce IRQ_HANDLED_MANY
On Fri, Feb 16 2024 at 04:59, Leonardo Bras wrote:
> In threaded IRQs, some irq handlers are able to handle many requests at a
> single run, but this is only accounted as a single IRQ_HANDLED when
> increasing threads_handled.
>
> In order to fix this, introduce IRQ_HANDLED_MANY, so the returned value of
> those IRQ handlers are able to signal that many IRQs got handled at that
> run.
>
> Is scenarios where there is no need to keep track of IRQ handled, convert
> it back to IRQ_HANDLED.
That's not really workable as you'd have to update tons of drivers just
to deal with that corner case. That's error prone and just extra
complexity all over the place.
This really needs to be solved in the core code.
Thanks,
tglx
Powered by blists - more mailing lists