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 from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
