On Tue, May 09 2023 at 13:02, Peter Zijlstra wrote: > On Mon, May 08, 2023 at 09:43:49PM +0200, Thomas Gleixner wrote: >> From: Thomas Gleixner <tglx@xxxxxxxxxxxxx> >> >> There is no harm to hold sparse_irq lock until the upcoming CPU completes >> in cpuhp_online_idle(). This allows to remove cpu_online() synchronization >> from architecture code. > > Uuuuuhh.. damn. Can you at the very least ammend the comment near > irq_lock_sparse() to mention these extra duties? Will do.
