[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e27238fc-259d-4537-9513-52d10006c321@kernel.org>
Date: Mon, 4 Aug 2025 13:00:22 +0200
From: Jiri Slaby <jirislaby@...nel.org>
To: Wladislav Wiebe <wladislav.wiebe@...ia.com>, tglx@...utronix.de,
corbet@....net, jirislaby@...nel.org
Cc: akpm@...ux-foundation.org, paulmck@...nel.org, rostedt@...dmis.org,
Neeraj.Upadhyay@....com, david@...hat.com, bp@...en8.de, arnd@...db.de,
fvdl@...gle.com, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
peterz@...radead.org
Subject: Re: [PATCH v5] genirq: add support for warning on long-running IRQ
handlers
On 04. 08. 25, 11:35, Wladislav Wiebe wrote:
> Introduce a mechanism to detect and warn about prolonged IRQ handlers.
> With a new command-line parameter (irqhandler.duration_warn_us=),
> users can configure the duration threshold in microseconds when a warning
> in such format should be emitted:
>
> "[CPU14] long duration of IRQ[159:bad_irq_handler [long_irq]], took: 1330 us"
>
> The implementation uses local_clock() to measure the execution duration of the
> generic IRQ per-CPU event handler.
Reviewed-by: Jiri Slaby <jirislaby@...nel.org>
--
js
suse labs
Powered by blists - more mailing lists