On Fri, Oct 17, 2025 at 11:57:28AM +0200, Jan Beulich wrote: > On 17.10.2025 11:19, Roger Pau Monné wrote: > > On Thu, Oct 16, 2025 at 09:32:29AM +0200, Jan Beulich wrote: > >> Following hpet_detach_channel(), IRQs may still occur: Ones may already > >> be in flight (both from before and after the last IRQ migration, i.e. on > >> possibly two distinct vectors targeting two different CPUs), and new ones > >> may still be raised as long as the channel is enabled. > > > > Description would need to be adjusted if nothing else, as it speaks > > about two distinct vectors which is no longer possible after patch 3. > > Oh, right - dropping the parenthesized part. > > >> Signed-off-by: Jan Beulich <[email protected]> > > > > With the above adjusted: > > > > Reviewed-by: Roger Pau Monné <[email protected]> > > Thanks, but as per the RFC remark: Do you then think this is actually > worthwhile despite what patch 3 does?
I don't think it will hurt, but I also think this can possibly wait after the code freeze, I don't see much win from doing it, and there's a risk we might get it wrong. Thanks, Roger.
