IRQ thread timeouts and affinity
Marc Zyngier
maz at kernel.org
Sat Oct 11 03:00:11 PDT 2025
On Fri, 10 Oct 2025 16:03:01 +0100,
Thierry Reding <thierry.reding at gmail.com> wrote:
>
> On Fri, Oct 10, 2025 at 03:18:13PM +0100, Marc Zyngier wrote:
> >
> > CPU hotplug is the main area of concern, and I'm pretty sure it breaks
> > this distribution mechanism (or the other way around). Another thing
> > is that if firmware isn't aware that 1:N interrupts can (or should)
> > wake-up a CPU from sleep, bad things will happen. Given that nobody
> > uses 1:N, you can bet that any bit of privileged SW (TF-A,
> > hypervisors) is likely to be buggy (I've already spotted bugs in KVM
> > around this).
>
> Okay, I can find out if CPU hotplug is a common use-case on these
> devices, or if we can run some tests with that.
It's not so much whether CPU hotplug is of any use to your particular
box, but whether this has any detrimental impact on *any* machine
doing CPU hotplug.
To be clear, this stuff doesn't go in if something breaks, no matter
how small.
M.
--
Without deviation from the norm, progress is not possible.
More information about the linux-arm-kernel
mailing list