From: Avi Kivity <avi@redhat.com>
To: Ryota Ozaki <ozaki.ryota@gmail.com>
Cc: Gleb Natapov <gleb@redhat.com>, dbareiro@gmx.net, kvm@vger.kernel.org
Subject: Re: CPU hotplug add seems broken
Date: Mon, 11 Jan 2010 12:23:05 +0200 [thread overview]
Message-ID: <4B4AFC09.3090909@redhat.com> (raw)
In-Reply-To: <5e93dcec1001110124l38d35ef7y4e92aa8b74aa810a@mail.gmail.com>
On 01/11/2010 11:24 AM, Ryota Ozaki wrote:
>
>> The problem is that there is no standard
>> way to hotplug CPUs in a PC. Linux implements the way UNISYS happen to do
>> it, but no other system do it like that. Windows implements it
>> differently and in the way that conflicts with Linux, so you can't
>> have working Linux implementation and pass Microsoft SVVP test at the
>> same time for instance.
>>
> Could I ask you what's the difference between the two implementations?
> Don't we have a possibility to have different implementations in qemu-kvm
> (and SeaBIOS)?
>
IMO we should stick with the unisys-derived implementation, port it to
SeaBIOS, and write a Windows driver for it. It has the advantage of
having support in Linux, and of being somewhat tested.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-11 10:23 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 [this message]
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
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=4B4AFC09.3090909@redhat.com \
--to=avi@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).