On Fri, Feb 07, 2014 at 05:11:26PM +0530, Preeti U Murthy wrote: > But observe the idle state "snooze" on powerpc. The power that this idle > state saves is through the lowering of the thread priority of the CPU. > After it lowers the thread priority, it is done. It cannot > "wait_for_interrupts". It will exit my_idle(). It is now upto the > generic idle loop to increase the thread priority if the need_resched > flag is set. Only an interrupt routine can increase the thread priority. > Else we will need to do it explicitly. And in such states which have a > polling nature, the cpu will not receive a reschedule IPI. > > That is why in the snooze_loop() we poll on need_resched. If it is set > we up the priority of the thread using HMT_MEDIUM() and then exit the > my_idle() loop. In case of interrupts, the priority gets automatically > increased.
You can poll without setting TS_POLLING/TIF_POLLING_NRFLAGS just fine and get the IPI if that is what you want. Depending on how horribly unprovisioned the thread gets at the lowest priority, that might actually be faster than polling and raising the prio whenever it does get ran. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
