From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 13 Dec 2018 15:53:21 +0100 From: Peter Zijlstra To: Sasha Levin Cc: Backport@sasha-vm, for@sasha-vm, cachelinestarvationonx86@sasha-vm, stable@vger.kernel.org, Will Deacon , Thomas Gleixner , Daniel Wagner Subject: Re: your mail Message-ID: <20181213145321.GK5289@hirez.programming.kicks-ass.net> References: <20181213140925.6179-1-bigeasy@linutronix.de> <20181213143336.GI2746@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181213143336.GI2746@sasha-vm> List-ID: On Thu, Dec 13, 2018 at 09:33:36AM -0500, Sasha Levin wrote: > On Thu, Dec 13, 2018 at 03:09:15PM +0100, Sebastian Andrzej Siewior wrote: > > Hi, > > > > this is a backport of commit 7aa54be297655 ("locking/qspinlock, x86: > > Provide liveness guarantee") for the v4.9 stable tree. > > For the v4.4 tree the ARCH_USE_QUEUED_SPINLOCKS option got disabled on > > x86. > > For v4.9 it has been decided to do a minimal backport of the final fix > > (including all its dependencies). > > With this backport I can't reproduce the issue in the latest v4.9-RT > > tree. I was able to boot (and use) an arm64 box with these patches so it > > is not broken in an abvious way. > > What about 4.14? I see that at least some of these patches are missing > there. 4.14 can have a simpler backport indeed