On Fri, 6 Mar 2015 13:19:21 +0100 Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx> wrote: > * Steven Rostedt | 2015-02-26 09:06:10 [-0500]: > > >If we can pull that off and remove all rtmutex trylocks from hardirq > >context, I would much rather do that. > > > >This hocus pocus coding is just going to lead us down the path of the > >black arts. I already have a black cat, so I'm good to go. > > Okay. So what is the fix for v3.14 and other trees where the rtmutex > reworked has been integrated? Revert the optimization like I did in > v3.18? Probably. I'm going to start looking at what's in 3.18 and start porting changes to 3.14 and earlier. I've only been updating the stable kernels to pull in the mainline stable updates. I haven't reverted anything (unless mainline stable caused things to be obsolete), nor have I added any updates. BTW, I'm going to start with 3.18-rt1 and see what's been added to the other -rt updates. If there's something I need that was added to 3.18-rt1 can you let me know. That is, if it wasn't marked with a stable-rt tag. My scripts will find those. -- Steve -- 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
