All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Kip Walker <kwalker@broadcom.com>, linux-kernel@vger.kernel.org
Cc: linux-mips@sgi.com
Subject: Re: init_idle reaped before final call
Date: Tue, 05 Mar 2002 13:57:09 -0800	[thread overview]
Message-ID: <292270000.1015365429@flay> (raw)
In-Reply-To: <3C8522EA.2A00E880@broadcom.com>
In-Reply-To: <3C8522EA.2A00E880@broadcom.com>

> I'm working with a (approximately) 2.4.17 kernel from the mips-linux
> tree (oss.sgi.com).
> 
> I'd like to propose removing the "__init" designation from init_idle in
> kernel/sched.c, since this is called from rest_init via cpu_idle. 
> Notice that rest_init isn't in an init section, and explicitly mentions
> that it's avoiding a race with free_initmem.  In my kernel (an SMP
> kernel running on a system with only 1 available CPU), cpu_idle isn't
> getting called until after free_initmem().
> 
> My CPU is MIPS, but it looks like x86 could experience the same problem.

I fixed something in this area for x86, looks like the same code path
for MIPS unless I'm misreading.

smp_init spins waiting on wait_init_idle until every cpu has done
init_idle. rest_init() isn't called until smp_init returns, so I'm not sure
how you could hit this (possibly there's a minute window after init_idle
clears the bit, but before it returns?).

M.


  reply	other threads:[~2002-03-05 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05 19:56 init_idle reaped before final call Kip Walker
2002-03-05 21:57 ` Martin J. Bligh [this message]
2002-03-05 22:15   ` Kip Walker
2002-03-05 23:33     ` Justin Carlson
  -- strict thread matches above, loose matches on Subject: below --
2002-03-05 19:58 Kip Walker
2002-03-05 22:06 Thomas Hood
2002-03-06  3:57 ` Keith Owens

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=292270000.1015365429@flay \
    --to=martin.bligh@us.ibm.com \
    --cc=kwalker@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@sgi.com \
    /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.