On Wed, Apr 09, 2014 at 11:14:38AM +0200, Stefan Bader wrote: > On 08.04.2014 14:21, Peter Zijlstra wrote: > > On Mon, Apr 07, 2014 at 08:56:58PM +0200, Peter Zijlstra wrote: > >> On Mon, Apr 07, 2014 at 08:16:24PM +0200, Toralf Förster wrote: > >> > >>> v3.14-10353-g2b3a8fd works fine AFAICS > >>> (BTW the fix is stable material, right ?) > >> > >> I'm fairly sure its not; its a rather invasive series; see: > >> > >> 2432e1364bbe x86: Nuke the supervisor_stack field in i386 thread_info > >> b807902a88c4 x86: Nuke GET_THREAD_INFO_WITH_ESP() macro for i386 > >> 0788aa6a23cb x86: Prepare removal of previous_esp from i386 thread_info > >> structure > >> 198d208df437 x86: Keep thread_info on thread stack in x86_32 > >> > >> Let me see if there's anything 'simpler' we can stuff in .13+ > > > > OK.. so could someone test the below patch to see if that makes things > > work for .13 and .14? > > Hi Peter, > > sorry I only had time to try 3.13 but that looks good. I was able to get kvm > up > and running for a longer than usual (without the patch) amount of time without > seeing any softlockups.
Great, I suppose I should go write a changelog and talk to Greg about how to get this into .13 and .14 stable. -- 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/