Re: [PATCH 1/6] irq_work: Re-raise pending irq_work after system resume

[Sebastian Andrzej Siewior]

On 2026-11-02 12:54:22 [+0200], Adrian Hunter wrote:
> 
> Yes CPUs remain online for suspend2idle, but currently the choice between
> suspend2idle and "deep" (S3) suspend is a user space choice,
> refer /sys/power/mem_sleep.  Many modern systems do not support S3
> anymore, but it has not gone away.
> 
> > 
> > Anyway, I'm torn; I would much rather make this trigger a WARN and have
> 
> AI now also identifies ftrace, BPF, GHES NMI, and #MC as possible causes,
> not just perf.  I haven't tried to confirm any of those.
> 
> And, belatedly, AI is now saying an irq_work raised before lapic_resume()
> might result in #GP if the APIC is left in xAPIC mode at resume.  Also
> not confirmed.

Could we flush this before similarly to what happens during CPU-hotplug.
The question is if this event can stay enqueued during suspend (and
handled on resume) or should be taken care before entering suspend.

Sebastian