From: Glauber Costa <glommer@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] Set bit 1 in disabled processor's _STA
Date: Mon, 18 May 2009 09:40:03 -0300 [thread overview]
Message-ID: <20090518124003.GS27295@poweredge.glommer> (raw)
In-Reply-To: <20090518114018.GB14536@redhat.com>
On Mon, May 18, 2009 at 02:40:18PM +0300, Gleb Natapov wrote:
> On Mon, May 18, 2009 at 08:39:43AM -0300, Glauber Costa wrote:
> > > Now I recall something on LKML about this. Well, in this case Linux
> > > shouldn't have used ACPI to invent its own way to do cpu hot-plug.
> > It didn't.
> > History shows that this method is what is used in some unisys machines,
> > which seems to be the only ones implementing this around.
> The questions are: What is "this" that linux currently implements, how
> windows expects CPU hot-plug to work, are there any real x86 hardware
> that supports CPU host-plug and what should we do about all this.
as I said, there are unisys machines that implements cpu hotplug.
The way they do it, is the way Linux kernel currently expects. The same way
we implement on our BIOS.
next prev parent reply other threads:[~2009-05-18 12:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 12:14 [PATCH] Set bit 1 in disabled processor's _STA Glauber Costa
2009-05-17 8:23 ` Gleb Natapov
2009-05-17 13:27 ` Glauber Costa
2009-05-17 14:30 ` Gleb Natapov
2009-05-17 15:06 ` Glauber Costa
2009-05-17 15:21 ` Gleb Natapov
2009-05-17 15:47 ` Glauber Costa
2009-05-18 6:58 ` Gleb Natapov
2009-05-17 14:31 ` Glauber Costa
2009-05-17 14:32 ` Gleb Natapov
2009-05-17 15:07 ` Glauber Costa
2009-05-17 15:30 ` Gleb Natapov
2009-05-17 20:07 ` Avi Kivity
2009-05-18 0:47 ` Glauber Costa
2009-05-18 5:17 ` Gleb Natapov
2009-05-18 5:44 ` Avi Kivity
2009-05-18 5:53 ` Gleb Natapov
2009-05-18 11:39 ` Glauber Costa
2009-05-18 11:40 ` Gleb Natapov
2009-05-18 12:40 ` Glauber Costa [this message]
2009-05-18 12:42 ` Gleb Natapov
2009-05-18 12:59 ` Glauber Costa
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=20090518124003.GS27295@poweredge.glommer \
--to=glommer@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@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