On 11/10/2014 00:29, Alan Hourihane wrote:
Yes, that's fine to do, and it's not strange. It is expected behaviour when you call Fselect(1,...) now.
If I understand well, Olivier used Fselect(1,...) to estimate the time slice? It worked by chance, as a side effect of the previous implementation.
Isn't there a better solution to know the time slice from user programs? Anyway, I still wonder why user programs could need that information.
I'll put back the Fselect(1,...) fix in the kernel.
Fine! So everything works again. -- Vincent Rivière