All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitri Sivanich <sivanich@sgi.com>
To: Cliff Wickman <cpw@sgi.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] hotplug cpus on ia64
Date: Wed, 4 Jun 2008 08:50:20 -0500	[thread overview]
Message-ID: <20080604135020.GB18993@sgi.com> (raw)
In-Reply-To: <20080603221759.GA19039@sgi.com>

On Tue, Jun 03, 2008 at 05:17:59PM -0500, Cliff Wickman wrote:
> 
> On Fri, May 30, 2008 at 03:36:54PM +0200, Peter Zijlstra wrote:
> > On Thu, 2008-05-29 at 11:32 -0500, Cliff Wickman wrote:
> > > I put in counters and see that schedule() is never again entered by cpu 17
> > > after it is downed the 3rd time.
> > > (it is entered after being up'd the first two times)
> > > 
> > > The kstopmachine thread is bound to cpu 17 by __stop_machine_run()'s call
> > > to kthread_bind().
> > > 
> > > A cpu does not schedule after being downed, of course.  But it does again
> > > after being up'd.  
> > > Why would the second up be different?  Following it, if the cpu is
> > > downed it never schedules again.
> > > 
> > > If I always bind kstopmachine to cpu 0 the problem disappears.
> > 
> > does:
> > 
> > echo -1 > /proc/sys/kernel/sched_rt_runtime_us
> > 
> > fix the problem?
> 
> Yes! It does. 
> 
> Dimitri Sivanich has run into what looks like a similar problem.
> Hope the above workaround is a good clue to its solution.

This fixes the problem I was seeing as well.

  reply	other threads:[~2008-06-04 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1K1l2y-0007bu-44@eag09.americas.sgi.com>
     [not found] ` <1212154614.12349.244.camel@twins>
2008-06-03 22:17   ` [BUG] hotplug cpus on ia64 Cliff Wickman
2008-06-04 13:50     ` Dimitri Sivanich [this message]
2008-06-05 12:49     ` Peter Zijlstra
2008-06-05 13:51       ` Dimitri Sivanich
2008-06-05 14:18         ` Peter Zijlstra
2008-06-10 10:19       ` Ingo Molnar
2008-05-13 14:33 [BUG] cpu hotplug vs scheduler Avi Kivity
2008-05-14  8:13 ` Dmitry Adamushko
2008-05-21 14:48   ` [BUG] hotplug cpus on ia64 Cliff Wickman

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=20080604135020.GB18993@sgi.com \
    --to=sivanich@sgi.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=cpw@sgi.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 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.