On Sun, May 31, 2015 at 08:39:04AM +0200, Mike Galbraith wrote: > I don't see why we can't just say no in can_migrate_task() if ->pi_lock > is held.
I suppose we could do that; what I really want to avoid is also requiring pi_lock for scheduling. The down-side of looking at pi_lock for migration is that there is no common point for migrating tasks, its all inside the classes, so we'd get to sprinkle it all over the place. -- 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/
