From: ebiederm@xmission.com (Eric W. Biederman)
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>,
stsp@aknet.ru, linux-kernel@vger.kernel.org
Subject: Re: the creation of boot_cpu_init() is wrong and accessing uninitialised data
Date: Sun, 02 Jul 2006 08:52:02 -0600 [thread overview]
Message-ID: <m1zmfs83fx.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1151600336.6186.9.camel@mulgrave.il.steeleye.com> (James Bottomley's message of "Thu, 29 Jun 2006 12:58:55 -0400")
James Bottomley <James.Bottomley@SteelEye.com> writes:
> On Wed, 2006-06-28 at 19:10 -0400, James Bottomley wrote:
>> I'm still compiling, so might have the results later this evening.
>
> Actually, ran into a 53c700 driver problem, but I can now verify that
> this patch works on voyager when booting with a non-zero CPU.
What is the point of using a non-zero logical cpu id?
I don't care about the apic id or the equivalent.
There are cases like machine_shutdown where we care about who
the boot cpu is so we can reboot on that cpu. As far as I know
the kernel has not abstraction to describe the boot cpu
except for giving it logical cpu id 0. Has an abstraction
been added that I'm not aware of?
Eric
next prev parent reply other threads:[~2006-07-02 14:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 2:45 the creation of boot_cpu_init() is wrong and accessing uninitialised data James Bottomley
2006-06-27 3:04 ` Andrew Morton
2006-06-27 3:36 ` James Bottomley
2006-06-27 5:03 ` Andrew Morton
2006-06-27 13:00 ` Keith Owens
2006-06-27 14:01 ` James Bottomley
2006-06-27 14:49 ` James Bottomley
2006-06-28 0:04 ` Andrew Morton
2006-06-28 2:45 ` James Bottomley
2006-06-28 2:57 ` Andrew Morton
2006-06-28 23:10 ` James Bottomley
2006-06-29 16:58 ` James Bottomley
2006-07-02 14:52 ` Eric W. Biederman [this message]
2006-07-02 15:06 ` James Bottomley
2006-07-02 15:37 ` Eric W. Biederman
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=m1zmfs83fx.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.ru \
/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.