All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Donald <gdonald@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: find_busiest_group divide error
Date: Wed, 16 Jul 2014 12:52:59 -0500	[thread overview]
Message-ID: <20140716175259.GA5956@gmail.com> (raw)
In-Reply-To: <20140716152736.GD19379@twins.programming.kicks-ass.net>

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

On Wed, Jul 16, 2014 at 05:27:36PM +0200, Peter Zijlstra wrote:
> Could you confirm if reverting caffcdd8d27ba78730d5540396ce72ad022aff2c
> cures things for you?
> 
> Otherwise there's two very similar issues, see also:
> 
>    lkml.kernel.org/r/20140716145546.GA6922@wolff.to

Cured.

I reverted caffcdd8d27ba78730d5540396ce72ad022aff2c which did nothing as
far as I can tell, then I removed the
two lines from http://marc.info/?l=linux-kernel&m=140552264825755, then
I added back the one line from
https://bugzilla.kernel.org/show_bug.cgi?id=80251#c8.

I ended up with

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index dc2927c..7c3674d 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -5848,7 +5848,6 @@ build_sched_groups(struct sched_domain *sd, int
cpu)
 
                group = get_group(i, sdd, &sg);
                cpumask_clear(sched_group_cpus(sg));
-               sg->sgp->power = 0;
                cpumask_setall(sched_group_mask(sg));
 
                for_each_cpu(j, span) {


Thanks.

-- 
Greg Donald

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2014-07-16 17:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 16:56 find_busiest_group divide error Greg Donald
2014-07-16 15:27 ` Peter Zijlstra
2014-07-16 16:40   ` Bruno Wolff III
2014-07-16 17:52   ` Greg Donald [this message]
2014-07-16 21:31     ` Dietmar Eggemann
2014-07-16 21:47       ` Greg Donald

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=20140716175259.GA5956@gmail.com \
    --to=gdonald@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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.