[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190416133315.GB17860@pauld.bos.csb>
Date: Tue, 16 Apr 2019 09:33:15 -0400
From: Phil Auld <pauld@...hat.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, bsegall@...gle.com,
torvalds@...ux-foundation.org, anton@...abs.org, efault@....de,
mingo@...nel.org, tglx@...utronix.de,
linux-tip-commits@...r.kernel.org
Subject: Re: [tip:sched/core] sched/fair: Limit sched_cfs_period_timer loop
to avoid hard lockup
On Tue, Apr 09, 2019 at 03:05:27PM +0200 Peter Zijlstra wrote:
> On Tue, Apr 09, 2019 at 08:48:16AM -0400, Phil Auld wrote:
> > Hi Ingo, Peter,
> >
> > On Wed, Apr 03, 2019 at 01:38:39AM -0700 tip-bot for Phil Auld wrote:
> > > Commit-ID: 06ec5d30e8d57b820d44df6340dcb25010d6d0fa
> > > Gitweb: https://git.kernel.org/tip/06ec5d30e8d57b820d44df6340dcb25010d6d0fa
> > > Author: Phil Auld <pauld@...hat.com>
> > > AuthorDate: Tue, 19 Mar 2019 09:00:05 -0400
> > > Committer: Ingo Molnar <mingo@...nel.org>
> > > CommitDate: Wed, 3 Apr 2019 09:50:23 +0200
> >
> > This commit seems to have gotten lost. It's not in tip and now the
> > direct gitweb link is also showing bad commit reference.
> >
> > Did this fall victim to a reset or something?
>
> It had (trivial) builds fails on 32 bit. I have a fixed up version
> around somewhere, but that hasn't made it back in yet.
Friendly ping...
Thanks,
Phil
--
Powered by blists - more mailing lists