On Fri, 20 Nov 2015, Peter Zijlstra wrote:
> On Fri, Nov 20, 2015 at 10:45:14AM +0100, Thomas Gleixner wrote:
>
> > The whole concept of faking idle is simply crap.
>
> :-)
>
> > If you want to avoid that stuff in the scheduler, then create a
> > mechanism which just defers the next timer interrupt for X
> > milliseconds and does not any fiddling with NOHZ state and such.
>
> Not sure that will actually result in the machine going idle. Device
> interrupts will still wake tasks and get them ran.
That's not what I meant. If you don't want to control all that from
the scheduler than you are back to that thread which "runs" at RT
priority and does
if (machine_on_fire) {
defer_timer_interrupt(5ms);
end = now + 5ms:
while (now < end)
mwait();
}
That's what the existing code does, but the above does not longer
claim it's idle and confuses the hell out of nohz and whatever. It's
just a "runaway" RT task which "hogs" the CPU for 5ms and makes the
next timer interrupt firing late.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
