From: Bill Davidsen <davidsen@tmr.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Justin Banks <justinb@bakbone.com>,
"Miller, Mike (OS Dev)" <Mike.Miller@hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: FW: Linux question
Date: Sat, 08 Mar 2008 12:07:35 -0500 [thread overview]
Message-ID: <47D2C7D7.2080301@tmr.com> (raw)
In-Reply-To: <874pbifit7.fsf@basil.nowhere.org>
Andi Kleen wrote:
> Bill Davidsen <davidsen@tmr.com> writes:
>
>
>> Here's an interesting question, why isn't there an "online" file for
>> each CPU?
>>
>
> There are still some problems with off lining CPU #0 on x86 at least,
> that is why it is not allowed. iirc they weren't very difficult so it
> would be probably fixable with some effort.
>
If that's the case I would think that making it read-only would be a
better solution, since I found this while creating a little tool to scan
and see what's online and what's not. Obviously there can be exception
cases for CPU0 and x86, but I would think that having the CPU0 for x86
be read-only would be a quirk, and handled in the kernel.
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
prev parent reply other threads:[~2008-03-08 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 19:33 FW: Linux question Miller, Mike (OS Dev)
2008-03-06 19:51 ` Cyrill Gorcunov
2008-03-06 20:38 ` Justin Banks
2008-03-07 18:43 ` Bill Davidsen
2008-03-07 19:13 ` Justin Banks
2008-03-07 19:14 ` Andi Kleen
2008-03-08 17:07 ` Bill Davidsen [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=47D2C7D7.2080301@tmr.com \
--to=davidsen@tmr.com \
--cc=Mike.Miller@hp.com \
--cc=andi@firstfloor.org \
--cc=justinb@bakbone.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