From: devik <devik@cdi.cz>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: <linux-kernel@vger.kernel.org>, <piggin@cyberone.com.au>
Subject: Re: [PATCH] sched isolcpus=1 related OOPS in 2.6.9
Date: Fri, 3 Dec 2004 19:15:58 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.33.0412031907271.493-200000@devix> (raw)
In-Reply-To: <41B09FFD.6070706@osdl.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 483 bytes --]
> You are correct, of course. If "isolcpus" is used, the isolated
> cpu(s) (in <cpu_isolated_map>) are not init like the remaining
> cpus are.
>
> I don't know what's intended here... but it's not the divide by 0.
A patch is attached which fixes problems with isolated
domains for me. I hope it is correct :-) I will try on
real SMP when I will be in work (now it boots on Boochs).
enjoy,
Martin Devera aka devik
Linux kernel QoS/HTB maintainer
http://luxik.cdi.cz/~devik/
[-- Attachment #2: Type: TEXT/PLAIN, Size: 1224 bytes --]
--- linux-2.6.9/kernel/sched.c Mon Oct 18 23:54:55 2004
+++ kernel/sched.c Fri Dec 3 19:06:04 2004
@@ -4480,7 +4480,7 @@
#ifdef CONFIG_NUMA
sd->span = nodemask;
#else
- sd->span = cpu_possible_map;
+ sd->span = cpu_default_map;
#endif
sd->parent = p;
sd->groups = &sched_group_phys[group];
@@ -4512,11 +4512,14 @@
/* Set up isolated groups */
for_each_cpu_mask(i, cpu_isolated_map) {
+ int group;
cpumask_t mask;
cpus_clear(mask);
cpu_set(i, mask);
init_sched_build_groups(sched_group_isolated, mask,
&cpu_to_isolated_group);
+ group = cpu_to_isolated_group(i);
+ sched_group_isolated[group].cpu_power = SCHED_LOAD_SCALE;
}
#ifdef CONFIG_NUMA
@@ -4532,7 +4535,7 @@
&cpu_to_phys_group);
}
#else
- init_sched_build_groups(sched_group_phys, cpu_possible_map,
+ init_sched_build_groups(sched_group_phys, cpu_default_map,
&cpu_to_phys_group);
#endif
@@ -4634,7 +4637,7 @@
cpus_or(groupmask, groupmask, group->cpumask);
cpumask_scnprintf(str, NR_CPUS, group->cpumask);
- printk(" %s", str);
+ printk(" %s[%ld]", str, group->cpu_power);
group = group->next;
} while (group != sd->groups);
next prev parent reply other threads:[~2004-12-03 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 15:42 devik
2004-12-03 16:28 ` devik
2004-12-03 17:18 ` Randy.Dunlap
2004-12-03 17:46 ` devik
2004-12-03 18:15 ` devik [this message]
2004-12-03 19:47 ` [PATCH] " Dimitri Sivanich
2004-12-03 20:21 ` devik
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=Pine.LNX.4.33.0412031907271.493-200000@devix \
--to=devik@cdi.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®