From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Gleb Natapov <gleb@redhat.com>,
Ryota Ozaki <ozaki.ryota@gmail.com>,
dbareiro@gmx.net, kvm@vger.kernel.org
Subject: Re: CPU hotplug add seems broken
Date: Mon, 11 Jan 2010 16:32:22 +0200 [thread overview]
Message-ID: <4B4B3676.7080801@redhat.com> (raw)
In-Reply-To: <4B4B2E4A.6080304@codemonkey.ws>
On 01/11/2010 03:57 PM, Anthony Liguori wrote:
> win2k8 supports CPU hotplug with VMware. I'd suggest someone fire up
> VMware and dump the ACPI tables to try and see how they're doing it.
> Otherwise, if someone has a physical machine that is known to do CPU
> hotplug with win2k8, an acpi dump would be useful there.
>
> I think it's easier to make sure Linux works with what Windows
> currently supports than vice versa.
>
Gleb found some presentation that describes Windows cpu hotplug as
something very similar to what we do today, so hopefully the whole issue
is just a bug or missing feature in the implementation.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-11 14:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 10:35 CPU hotplug add seems broken Ryota Ozaki
2010-01-09 19:30 ` Daniel Bareiro
2010-01-10 6:39 ` Gleb Natapov
2010-01-10 8:33 ` Ryota Ozaki
2010-01-10 8:43 ` Gleb Natapov
2010-01-11 9:24 ` Ryota Ozaki
2010-01-11 9:32 ` Gleb Natapov
2010-01-11 10:21 ` Ryota Ozaki
2010-01-11 10:23 ` Avi Kivity
2010-01-11 10:24 ` Gleb Natapov
2010-01-11 10:25 ` Avi Kivity
2010-01-11 10:42 ` Gleb Natapov
2010-01-11 10:50 ` Avi Kivity
2010-01-11 10:53 ` Gleb Natapov
2010-01-11 10:58 ` Avi Kivity
2010-01-11 11:03 ` Gleb Natapov
2010-01-11 11:06 ` Avi Kivity
2010-01-11 12:18 ` Gleb Natapov
2010-01-11 13:57 ` Anthony Liguori
2010-01-11 14:32 ` Avi Kivity [this message]
2010-01-11 10:30 ` Ryota Ozaki
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=4B4B3676.7080801@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=dbareiro@gmx.net \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ozaki.ryota@gmail.com \
/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.