From: Glauber Costa <glommer@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] Set bit 1 in disabled processor's _STA
Date: Sun, 17 May 2009 21:47:49 -0300 [thread overview]
Message-ID: <20090518004749.GQ27295@poweredge.glommer> (raw)
In-Reply-To: <4A106E83.6080302@redhat.com>
On Sun, May 17, 2009 at 11:07:31PM +0300, Avi Kivity wrote:
> Gleb Natapov wrote:
>>
>> Theoretically we can provide different values for different OSes, but
>> this is just a guess work since there is no any documentation how CPU
>> hot-plug should work on x86.
>>
>
> ACPI in fact supports this, but I hope we don't have to do that.
I believe it actually makes sense. It may even ease the acception into upstream projects.
Note that cpu hotplug is totally non specified by ACPI. This implementation is "what linux
expects", and does not work on windows at all (and I imagine it may not work on other OSes
as well). For this case, it might make sense to provide different values for different OSes.
next prev parent reply other threads:[~2009-05-18 0:42 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 [this message]
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
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=20090518004749.GQ27295@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