On Thu, 2016-03-24 at 11:44 +0100, Thomas Gleixner wrote: > > > On the bright side, with the busted migrate enable business reverted, > > plus one dinky change from me [1], master-rt.today has completed 100 > > iterations of Steven's hotplug stress script along side endless > > futexstress, and is happily doing another 900 as I write this, so the > > next -rt should finally be hotplug deadlock free. > > > > Thomas's state machinery seems to work wonders. 'course this being > > hotplug, the other shoe will likely apply itself to my backside soon. > > That's a given :) blk-mq applied it shortly after I was satisfied enough to poke xmit. > I really wonder what makes the change. The only thing which comes to my mind > is the enforcement of running the online and down_prepare callbacks on the > plugged cpu instead of doing it wherever the scheduler decides to run it. No idea, but it certainly seems.. well, markedly less brick like. > > 1. nest module_mutex inside hotplug_lock to prevent bloody systemd > > -udevd from blocking in migrate_disable() while holding kernfs_mutex > > during module load, putting a quick end to hotplug stress testing. > > Did I miss a patch here or is that still in your pile? You didn't miss it, it wasn't tested enough to consider sending.. and now I'm starting down the familiar "next" path again. Oh dear. -Mike -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
