as a sidenote: if we know -- like here -- that the next IRQ will be issuedsoon, in approximately 1.75 ms (well, at least on my system), might it makesense to make tick_nohz_get_sleep_length() smarter to know about this?