From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: 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 14:18:55 +0200 [thread overview]
Message-ID: <20100111121855.GM7549@redhat.com> (raw)
In-Reply-To: <4B4B0630.8010509@redhat.com>
On Mon, Jan 11, 2010 at 01:06:24PM +0200, Avi Kivity wrote:
> On 01/11/2010 01:03 PM, Gleb Natapov wrote:
> >
> >>No, but I'm not really worried about that.
> >>
> >So you want to introduce something that we know upset Windows without
> >looking into alternatives.
>
> I don't want to drop support for existing guests unless I have to.
>
Neither do I and I would be happy with what we had if SVVP wouldn't
complain. So we need some kind of fix, or exception for the test.
> >And as far as I remember upstream position
> >on the UNISYS way was negative, did this change?
>
> I don't see anything fundamentally wrong with the unisys
> implementation. True, it's not written to any spec, but neither is
> anything we can come up with (unless we find a spec for cpu
> hotplug).
>
--
Gleb.
next prev parent reply other threads:[~2010-01-11 12:19 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 [this message]
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=20100111121855.GM7549@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=dbareiro@gmx.net \
--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).