public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Robin Holt <holt@sgi.com>
Cc: Ingo Molnar <mingo@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: Commit cb83b62 fails to boot with a divide by zero error.
Date: Fri, 11 May 2012 16:33:10 +0200	[thread overview]
Message-ID: <1336746790.1017.17.camel@twins> (raw)
In-Reply-To: <20120511133938.GG3751@sgi.com>

On Fri, 2012-05-11 at 08:39 -0500, Robin Holt wrote:

> We found that reverting the commit:
> cb83b62 (x86/sched/core) sched/numa: Rewrite the CONFIG_NUMA sched domain support
> 
> also got things working.

there's a particularly stupid bug in that code



---
Subject: sched, numa: Fix the new NUMA topology bits
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
Date: Fri May 11 00:56:20 CEST 2012

There's no need to convert a node number to a node number by
pretending its a cpu number..

Reported-by: Yinghai Lu <yinghai@kernel.org>
Reported-and-Tested-by: Greg Pearson <greg.pearson@hp.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
 kernel/sched/core.c |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -6378,8 +6378,7 @@ static void sched_init_numa(void)
 			sched_domains_numa_masks[i][j] = mask;
 
 			for (k = 0; k < nr_node_ids; k++) {
-				if (node_distance(cpu_to_node(j), k) >
-						sched_domains_numa_distance[i])
+				if (node_distance(j, k) > sched_domains_numa_distance[i])
 					continue;
 
 				cpumask_or(mask, mask, cpumask_of_node(k));


  reply	other threads:[~2012-05-11 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 13:39 Commit cb83b62 fails to boot with a divide by zero error Robin Holt
2012-05-11 14:33 ` Peter Zijlstra [this message]
2012-05-11 15:05   ` Robin Holt
2012-05-11 15:36     ` Peter Zijlstra
2012-05-11 15:55       ` Robin Holt
2012-05-11 16:01         ` Peter Zijlstra
2012-05-14 10:48         ` Ingo Molnar
2012-05-14 12:40           ` Robin Holt

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=1336746790.1017.17.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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