From: Peter Zijlstra <peterz@infradead.org>
To: Jan Stancek <jstancek@redhat.com>
Cc: alex.shi@intel.com, guz.fnst@cn.fujitsu.com, mingo@redhat.com,
jolsa@redhat.com, riel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] scheduler doesn't balance thread to idle cpu for 3 seconds
Date: Thu, 28 Jan 2016 18:49:03 +0100 [thread overview]
Message-ID: <20160128174903.GV6356@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <56AA39D6.4070509@redhat.com>
On Thu, Jan 28, 2016 at 04:55:02PM +0100, Jan Stancek wrote:
> On 01/27/2016 03:52 PM, Jan Stancek wrote:
> > Hello,
> >
> > pthread_cond_wait_1/2 [1] is rarely failing for me on 4.5.0-rc1,
> > on x86_64 KVM guest with 2 CPUs.
> >
> > This test [1]:
> > - spawns 2 SCHED_RR threads
> > - first thread with higher priority sets alarm for 2 seconds and blocks on condition
> > - second thread with lower priority is busy looping for 5 seconds
> > - after 2 seconds alarm signal arrives and handler signals condition
> > - high priority thread should resume running
>
> I have slightly modified testcase, so it will finish immediately when high prio
> thread is done. And also to allow it to compile outside of openposix testsuite.
Yeah, I 'fixed' the testcase too.
So I've had it run for almost 2 hours without a single fail. I've
hot-plugged my cpu count down to 2.
How long should I have to wait for a fail?
next prev parent reply other threads:[~2016-01-28 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 14:52 Jan Stancek
2016-01-28 15:55 ` Jan Stancek
2016-01-28 17:49 ` Peter Zijlstra [this message]
2016-01-28 18:43 ` Jan Stancek
2016-01-29 10:15 ` Peter Zijlstra
2016-01-29 10:33 ` Jan Stancek
2016-02-08 13:40 ` Jan Stancek
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=20160128174903.GV6356@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alex.shi@intel.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=jolsa@redhat.com \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=riel@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome