All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: ego@in.ibm.com
Cc: Peter Zijlstra <peterz@infradead.org>,
	"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
	Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: specjbb2005 and aim7 regression with 2.6.32-rc kernels
Date: Mon, 09 Nov 2009 10:57:17 +0100	[thread overview]
Message-ID: <1257760637.7124.26.camel@marge.simson.net> (raw)
In-Reply-To: <20091109094425.GA26733@in.ibm.com>

On Mon, 2009-11-09 at 15:14 +0530, Gautham R Shenoy wrote:
> On Mon, Nov 09, 2009 at 10:15:04AM +0100, Peter Zijlstra wrote:
> > On Mon, 2009-11-09 at 08:09 +0100, Mike Galbraith wrote:
> > > +       smp_read_barrier_depends();
> > >         cpumask_setall(cpus);
> > > +       cpumask_and(cpus, cpus, cpu_online_mask);
> > 
> > 
> > how about: cpumask_copy(cpus, cpu_online_mask); ?
> > 
> > Also, iirc cpu_online_mask is guaranteed stable when preemption is
> > disabled, otherwise you need to use get/put_online_cpus(), an
> > rmb_depends() won't do.
> 
> preempt_disable() guarantees that any cpus won't go offline, since we
> use stop_machine() to take CPUs offline. I don't think it provides cover
> against new cpus coming online.

That's exactly the problem I'm having with newidle.  Without that
barrier, even with the cpumask_and(), it still balances offline cpus.

	-Mike


  reply	other threads:[~2009-11-09  9:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06  7:38 specjbb2005 and aim7 regression with 2.6.32-rc kernels Zhang, Yanmin
2009-11-06  8:02 ` Mike Galbraith
2009-11-06  8:04 ` Ingo Molnar
2009-11-09  6:19   ` Zhang, Yanmin
2009-11-09  7:09     ` Mike Galbraith
2009-11-09  9:15       ` Peter Zijlstra
2009-11-09  9:44         ` Gautham R Shenoy
2009-11-09  9:57           ` Mike Galbraith [this message]
2009-11-09  9:55         ` Mike Galbraith

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=1257760637.7124.26.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=ego@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=yanmin_zhang@linux.intel.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 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.