I was trying to test this in my 8 way NUMA box, but this patch
seems to have lost half of the wait_init_idle fix that I put
in a while back. I'm not sure if this is deliberate or not, but
I suspect not, as you only removed part of it, and from your
comment below (from a previous email), I think you understand
the reasoning behind it:
> the new rules are this: no schedule() must be called before all bits in
> wait_init_idle are clear. I'd suggest for you to add this to the top of
> schedule():
>
> if (wait_init_idle)
> BUG();
Anyway, the machine won't boot without this fix, so I tried adding
it back in, and now it boots just fine. Patch is attached below.
If the removal was accidental, please could you add it back in
as below ... if not, could we discuss why this was removed, and
maybe we can find another way to fix the problem?
Meanwhile, I'll try to knock out some benchmark figures with the
new scheduler code in place on the 8 way NUMA and a 16 way
NUMA ;-)
Martin.
diff -urN linux-2.4.18-pre4.old/init/main.c linux-2.4.18-pre4.new/init/main.c
--- linux-2.4.18-pre4.old/init/main.c Wed Jan 23 18:26:56 2002
+++ linux-2.4.18-pre4.new/init/main.c Wed Jan 23 18:27:04 2002
@@ -508,6 +508,14 @@
smp_threads_ready=1;
smp_commence();
+
+ /* Wait for the other cpus to set up their idle processes */
+ printk("Waiting on wait_init_idle (map = 0x%lx)\n", wait_init_idle);
+ while (wait_init_idle) {
+ cpu_relax();
+ barrier();
+ }
+ printk("All processors have done init_idle\n");
}
#endif
diff -urN linux-2.4.18-pre4.old/kernel/sched.c linux-2.4.18-pre4.new/kernel/sched.c
--- linux-2.4.18-pre4.old/kernel/sched.c Wed Jan 23 18:26:56 2002
+++ linux-2.4.18-pre4.new/kernel/sched.c Wed Jan 23 18:27:09 2002
@@ -1221,6 +1221,8 @@
spin_unlock(&rq2->lock);
}
+extern unsigned long wait_init_idle;
+
void __init init_idle(void)
{
runqueue_t *this_rq = this_rq(), *rq = current->array->rq;
@@ -1237,6 +1239,7 @@
current->state = TASK_RUNNING;
double_rq_unlock(this_rq, rq);
current->need_resched = 1;
+ clear_bit(cpu(), &wait_init_idle);
__restore_flags(flags);
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/