From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jmoyer@redhat.com, Arjan van de Ven <arjanv@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: finding out the boot cpu number from userspace
Date: Mon, 02 Aug 2004 11:49:02 -0700 [thread overview]
Message-ID: <35890000.1091472541@[10.10.2.4]> (raw)
In-Reply-To: <1091468548.810.3.camel@localhost.localdomain>
>> Eric went to some lengths to migrate us back to the original boot CPU
>> before kexec'ing. I think this is unnecessary - the new kernel should
>> handle booting on any CPU just fine (there was a panic in there at one
>> point if the boot CPU didn't match the BIOS's spec'ed one, but I removed
>> it).
>
> Several systems have broken SMM or BIOS functionality that requires the
> *real* boot processor is used. The panic was correct and should be
> restored. See apm_power_off() for one example.
Ah, OK didn't know that ... however, I'm not convinced that panicing is
really that useful ... what happens if you proceed? IIRC, this is before
console_init as well, so people won't even see the error. At least it
should only do that on machines that are borked in such a fashion - 99% of
machines will work fine, AFAICS.
M.
next prev parent reply other threads:[~2004-08-02 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 12:16 Arjan van de Ven
2004-08-02 13:37 ` Dave Jones
2004-08-02 14:13 ` Alan Cox
2004-08-02 14:30 ` Zwane Mwaikambo
2004-08-02 14:46 ` Richard B. Johnson
2004-08-02 15:50 ` Martin J. Bligh
2004-08-02 16:58 ` Jeff Moyer
2004-08-02 17:23 ` Martin J. Bligh
2004-08-02 17:42 ` Alan Cox
2004-08-02 18:49 ` Martin J. Bligh [this message]
2004-08-02 18:23 ` Alan Cox
2004-08-02 20:08 ` Chris Wedgwood
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='35890000.1091472541@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=jmoyer@redhat.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®