From: Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: CPU hotplug boot change for IA64
Date: Fri, 02 Aug 2002 22:18:01 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905898@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905894@msgid-missing>
Hi David,
Sorry, I missed to remove that. :-(
cpu_initialized (or something like that) is needed when
CPU Hot Plug is implemented.
__cpu_up() must detect that the CPU has already been initialized
and but offlined or the CPU hasn't been initialized.
But for 2.5.29, such the variable isn't necessary.
And as you pointed out, it should not be in setup.c.
I'll update the patch and send it later.
Regards,
Kimi
On Fri, 2 Aug 2002 14:44:16 -0700
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> What's the reason for putting cpu_initialize in setup.c instead of
> smp.c? Also, I much prefer to have all global variables declared in
> header files; especially for special things that are marked __init or
> __devinit, etc. Nothing worse than someone accidentally trying to use
> the variable after its gone. (Yes, there are other offenders, but
> that's no reason to add to the problem.)
--
Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>
next prev parent reply other threads:[~2002-08-02 22:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 21:44 [Linux-ia64] Re: CPU hotplug boot change for IA64 David Mosberger
2002-08-02 22:18 ` Kimio Suganuma [this message]
2002-08-03 0:53 ` Kimio Suganuma
2002-08-03 3:29 ` Rusty Russell
2002-08-03 4:10 ` Kimio Suganuma
2002-08-05 1:19 ` Rusty Russell
2002-08-05 4:33 ` Andrew Morton
2002-08-06 18:33 ` Erich Focht
2002-08-06 20:26 ` Kimio Suganuma
2002-08-08 4:19 ` Kimio Suganuma
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=marc-linux-ia64-105590701905898@msgid-missing \
--to=k-suganuma@mvj.biglobe.ne.jp \
--cc=linux-ia64@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