[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181214071826.GE31355@kroah.com>
Date: Fri, 14 Dec 2018 08:18:26 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Henrik Austad <henrik@...tad.us>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
stable@...r.kernel.org, Henrik Austad <haustad@...co.com>,
Peter Zijlstra <peterz@...radead.org>, juri.lelli@....com,
bigeasy@...utronix.de, rostedt@...dmis.org,
mathieu.desnoyers@...icios.com, jdesfossez@...icios.com,
dvhart@...radead.org, bristot@...hat.com,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 00/17] Backport rt/deadline crash and the ardous story of
FUTEX_UNLOCK_PI to 4.4
On Mon, Nov 19, 2018 at 12:27:21PM +0100, Henrik Austad wrote:
> On Fri, Nov 09, 2018 at 11:35:31AM +0100, Henrik Austad wrote:
> > On Fri, Nov 09, 2018 at 11:07:28AM +0100, Henrik Austad wrote:
> > > From: Henrik Austad <haustad@...co.com>
> > >
> > > Short story:
> >
> > Sorry for the spam, it looks like I was not very specific in /which/
> > version I targeted this to, as well as not providing a full Cc-list for the
> > cover-letter.
>
> Gentle prod. I realize this was sent out just before plumbers and that
> people had pretty packed agendas, so a small nudge to gain a spot closer to
> the top of the inbox :)
>
> This series has now been running on an arm64 system for 9 days without any
> issues and pi_stress showed a dramatic improvement from ~30 seconds and up
> to several ours (it finally deadlocked at 3.9e9 inversions).
>
> I'd greatly appreciate if someone could give the list of patches a quick
> glance to verify that I got all the required patches and then if it could
> be added to 4.4.y.
This is a really intrusive series of patches, and without some testing
and verification by others, I am really reluctant to take these patches.
Why not just move to the 4.9.y tree, or better yet, 4.19.y to resolve
this issue for your systems?
thanks,
greg k-h
Powered by blists - more mailing lists