From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mgalbraith@suse.de, ahh@google.com,
bsegall@google.com, torvalds@linux-foundation.org,
matt@codeblueprint.co.uk, morten.rasmussen@arm.com,
pjt@google.com, pkondeti@infradead.org, tglx@linutronix.de,
byungchul.park@lge.com, mingo@kernel.org, rgkernel@gmail.com
Subject: Re: Bisection: Lost wakeups from b5179ac70de8
Date: Tue, 24 May 2016 05:50:18 -0700 [thread overview]
Message-ID: <20160524125018.GT3825@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160524090455.GF3192@twins.programming.kicks-ass.net>
On Tue, May 24, 2016 at 11:04:55AM +0200, Peter Zijlstra wrote:
> On Mon, May 23, 2016 at 07:04:10AM -0700, Paul E. McKenney wrote:
> > Hello, Peter,
> >
> > Current mainline doesn't do well with RCU torture testing, and the
> > symptom once again looks like lost wakeups. Thankfully, this time each
> > run takes only about an hour, and the false-positive/-negative rate
> > is negligible. This means that for the first time ever, "git bisect"
> > actually did something useful for me. The first bad commit is:
> >
> > b5179ac70de8 ("sched/fair: Prepare to fix fairness problems on migration").
> >
>
> Yeah, we have a patch for that.. I'll go writes a Changelog for it and
> put it to sched/urgent.
>
> See lkml.kernel.org/r/20160523091907.GD15728@worktop.ger.corp.intel.com
Thank you, will give it a shot.
Thanx, Paul
prev parent reply other threads:[~2016-05-24 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 14:04 Bisection: Lost wakeups from b5179ac70de8 Paul E. McKenney
2016-05-24 9:04 ` Peter Zijlstra
2016-05-24 12:50 ` Paul E. McKenney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160524125018.GT3825@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=ahh@google.com \
--cc=bsegall@google.com \
--cc=byungchul.park@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mgalbraith@suse.de \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=pkondeti@infradead.org \
--cc=rgkernel@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.