On Mon, Aug 29, 2016 at 12:53:30PM -0400, Chris Metcalf wrote:

Would it be cleaner to just replace the set_tsk_need_resched() call
with something like:

    set_current_state(TASK_INTERRUPTIBLE);
    schedule();
    __set_current_state(TASK_RUNNING);

or what would you recommend?

That'll just get you to sleep _forever_...

Or, as I said, just doing a busy loop here while testing to see
if need_resched or signal had been set?

Why do you care about need_resched() and or signals? How is that related
to the tick being stopped or not?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>