From: Ingo Molnar <mingo@elte.hu>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Dmitry Adamushko <dmitry.adamushko@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Avi Kivity <avi@qumranet.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [BUG] CFS vs cpu hotplug
Date: Mon, 30 Jun 2008 11:17:11 +0200 [thread overview]
Message-ID: <20080630091711.GA26637@elte.hu> (raw)
In-Reply-To: <20080630090744.GB6598@osiris.boeblingen.de.ibm.com>
* Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> On Sun, Jun 29, 2008 at 12:16:56AM +0200, Dmitry Adamushko wrote:
> > Hello,
> >
> >
> > it seems to be related to migrate_dead_tasks().
> >
> > Firstly I added traces to see all tasks being migrated with
> > migrate_live_tasks() and migrate_dead_tasks(). On my setup the problem
> > pops up (the one with "se == NULL" in the loop of
> > pick_next_task_fair()) shortly after the traces indicate that some has
> > been migrated with migrate_dead_tasks()). btw., I can reproduce it
> > much faster now with just a plain cpu down/up loop.
> >
> > [disclaimer] Well, unless I'm really missing something important in
> > this late hour [/desclaimer] pick_next_task() is not something
> > appropriate for migrate_dead_tasks() :-)
> >
> > the following change seems to eliminate the problem on my setup
> > (although, I kept it running only for a few minutes to get a few
> > messages indicating migrate_dead_tasks() does move tasks and the
> > system is still ok)
> >
> > [ quick hack ]
> >
> > @@ -5887,6 +5907,7 @@ static void migrate_dead_tasks(unsigned int dead_cpu)
> > next = pick_next_task(rq, rq->curr);
> > if (!next)
> > break;
> > + next->sched_class->put_prev_task(rq, next);
> > migrate_dead(dead_cpu, next);
> >
> > }
>
> Thanks Dmitry! With your patch I cannot reproduce the bug anymore.
thanks - it passed my testing too. It's lined up for v2.6.26 merge, in
tip/sched/urgent.
Avi, does this patch fix your CPU hotplug problems too?
Ingo
next prev parent reply other threads:[~2008-06-30 9:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 16:19 [BUG] CFS vs cpu hotplug Heiko Carstens
2008-06-19 18:05 ` Peter Zijlstra
2008-06-19 18:14 ` Peter Zijlstra
2008-06-19 21:14 ` Heiko Carstens
2008-06-19 21:26 ` Peter Zijlstra
2008-06-19 21:17 ` Heiko Carstens
2008-06-19 21:32 ` Peter Zijlstra
2008-06-19 21:49 ` Heiko Carstens
2008-06-20 8:51 ` Peter Zijlstra
2008-06-20 22:19 ` Heiko Carstens
2008-06-20 11:44 ` Dmitry Adamushko
2008-06-20 22:23 ` Heiko Carstens
2008-06-25 22:12 ` Dmitry Adamushko
2008-06-28 22:16 ` Dmitry Adamushko
2008-06-29 6:55 ` Ingo Molnar
2008-06-30 9:07 ` Heiko Carstens
2008-06-30 9:17 ` Ingo Molnar [this message]
2008-07-01 9:22 ` Lai Jiangshan
2008-07-01 9:31 ` Ingo Molnar
2008-07-01 10:09 ` Lai Jiangshan
2008-07-02 7:13 ` Lai Jiangshan
2008-07-02 8:50 ` Dmitry Adamushko
2008-07-02 9:23 ` Lai Jiangshan
2008-07-07 10:26 ` Miao Xie
2008-07-07 11:31 ` Dmitry Adamushko
-- strict thread matches above, loose matches on Subject: below --
2008-07-09 22:32 Dmitry Adamushko
2008-07-10 7:30 ` Heiko Carstens
2008-07-10 7:39 ` Ingo Molnar
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=20080630091711.GA26637@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=avi@qumranet.com \
--cc=dmitry.adamushko@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox