From: Andi Kleen <ak@suse.de>
To: Keith Owens <kaos@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cpu_up not called for boot cpu
Date: 28 Jun 2006 17:50:57 +0200 [thread overview]
Message-ID: <p731wt9xori.fsf@verdi.suse.de> (raw)
In-Reply-To: <8054.1151466063@kao2.melbourne.sgi.com>
Keith Owens <kaos@sgi.com> writes:
> cpu_up() is only called for secondary cpus, not for the boot cpu. That
> means that code hooked into the cpu_chain notifier never gets called
> for the boot cpu, which prevents additional subsystems from taking
> action for the boot cpu. So how are additional subsystems meant to be
> initialised for the boot cpu?
They ought to initialize themselves for the already online cpus
when they start.
Any other way would make them lose CPUs if they were loaded
after the other CPUs are added.
-Andi
prev parent reply other threads:[~2006-06-28 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 3:41 Keith Owens
2006-06-28 7:55 ` Heiko Carstens
2006-06-28 15:50 ` Andi Kleen [this message]
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=p731wt9xori.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=kaos@sgi.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
all inboxes | Powered by JetHome®