On Tue, May 20, 2014 at 06:24:36PM +0200, Frederic Weisbecker wrote: > Of course one can argue that we can find out that the task is resuming in > userspace from > CPU 0 scheduler entry without the need for previous context tracking, but I > couldn't find safe > solution for that. This is because probing on user/kernel boundaries can only > be done > in the soft way, throught explicit function calls. So there is an inevitable > shift > between soft and hard boundaries, between what we probe and what we can guess.
you can hook into set_task_cpu(), not sure its going to be pretty, but that is _the_ place to hook migration related nonsense. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
