From: Thomas Gleixner <tglx@linutronix.de>
To: Wladislav Wiebe <wladislav.wiebe@nokia.com>,
anna-maria@linutronix.de, frederic@kernel.org, mingo@kernel.org
Cc: akpm@linux-foundation.org, bigeasy@linutronix.de,
peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irq: add support for warning on long-running IRQ handlers
Date: Tue, 01 Jul 2025 09:37:05 +0200 [thread overview]
Message-ID: <87frfgmkf2.ffs@tglx> (raw)
In-Reply-To: <9dcfe1fb-0361-4d13-a4d5-fbc274f68db7@nokia.com>
On Tue, Jul 01 2025 at 08:10, Wladislav Wiebe wrote:
> On 30/06/2025 17:42, Thomas Gleixner wrote:
>> Define sufficient. That really depends on your use case. For a real-time
>> system a hard interrupt handler running longer than a few microseconds
>> can be problematic.
>>
>> So instead of adding some single purpose mechanism, can we please add
>> something flexible which can be used for a wide range of scenarios.
>
> the initial goal was to cover regular non-RT cores, as on isolated/tickless cores
> we should not have device interrupts.
Who is 'we'? If you refer to your use case that might be correct, but
you cannot make assumptions about the rest of the world. Real-Time
systems are as divers in setup and configuration as anything else.
Thanks,
tglx
next prev parent reply other threads:[~2025-07-01 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 12:46 [PATCH] irq: add support for warning on long-running IRQ handlers Wladislav Wiebe
2025-06-30 13:25 ` Peter Zijlstra
2025-06-30 13:59 ` Wladislav Wiebe
2025-07-02 9:06 ` Peter Zijlstra
2025-07-02 9:14 ` Wladislav Wiebe
2025-06-30 15:42 ` Thomas Gleixner
2025-07-01 6:10 ` Wladislav Wiebe
2025-07-01 7:37 ` Thomas Gleixner [this message]
2025-07-15 8:23 ` Wladislav Wiebe
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=87frfgmkf2.ffs@tglx \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=wladislav.wiebe@nokia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.