public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Matthew C. Dobson [imap]" <colpatch@us.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sched domains bringup race?
Date: Fri, 16 Jul 2004 13:03:53 +1000	[thread overview]
Message-ID: <40F74599.7000606@yahoo.com.au> (raw)
In-Reply-To: <1089944026.32312.47.camel@nighthawk>

Dave Hansen wrote:
> I keep getting oopses for the non-boot CPU in find_busiest_group(). 
> This occurs the first time that the CPU goes idle.  Those groups are set
> up in sched_init_smp(), which is called after smp_init():
> 
> static int init(void * unused)
> {
> 	...
>         fixup_cpu_present_map();
>         smp_init();
>         sched_init_smp();
> 
> But, the idle threads for the secondary CPUs are initialized in
> smp_init().  So, what happens when a CPU tries to schedule (using sched
> domains) before sched_init_smp() completes?  I think it goes boom! :)
> 

It shouldn't because sched_init sets up dummy domains for
all runqueues.

Obviously something is going wrong somewhere though.

  reply	other threads:[~2004-07-16  3:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16  2:13 sched domains bringup race? Dave Hansen
2004-07-16  3:03 ` Nick Piggin [this message]
2004-07-16  3:30   ` Dave Hansen
2004-07-16  3:46     ` Nick Piggin
2004-07-16  5:27       ` Nick Piggin
2004-07-18 20:45 ` Keshavamurthy Anil S
2004-07-19  7:31   ` Nick Piggin
2004-07-22 21:55     ` Nathan Lynch
2004-07-22 23:23       ` Keshavamurthy Anil S
2004-07-23  0:33       ` Nick Piggin

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=40F74599.7000606@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=colpatch@us.ibm.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.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