From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Andre Przywara <andre.przywara@amd.com>,
Ricardo Martins <ricardo.martins.br@gmail.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM Processor cache size
Date: Mon, 02 Aug 2010 17:22:10 -0500 [thread overview]
Message-ID: <4C574512.6030903@codemonkey.ws> (raw)
In-Reply-To: <4C56C353.7020607@redhat.com>
On 08/02/2010 08:08 AM, Avi Kivity wrote:
>> I sent a patch to include the cache size when using -cpu host, but
>> this has been n'acked because the benefit is not clear.
>
>
> Anthony, why was this NACKed?
I didn't NACK it.
My concern is that we're still not handling live migration with -cpu
host in any meaningful way. Exposing more details without addressing
live migration is going to increase the likelihood of major failure.
We need to add cpuid information to live migration such that we can
generate a graceful failure during migration. Really, we shouldn't have
taken -cpu host in the first place without this.
Regards,
Anthony Liguori
> First, there are programs which query the cache size. That's why
> it's exposed! Second, -cpu host is for exposing as many host cpu
> features as we can, not just those we have an immediate use for. It's
> like 'cp -a' dropping attributes the author didn't care about.
>
next prev parent reply other threads:[~2010-08-02 22:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 11:45 KVM Processor cache size Ricardo Martins
2010-08-02 12:51 ` Andre Przywara
2010-08-02 13:08 ` Avi Kivity
2010-08-02 22:22 ` Anthony Liguori [this message]
2010-08-02 22:35 ` Andre Przywara
2010-08-02 23:38 ` Anthony Liguori
2010-08-03 5:38 ` Avi Kivity
2010-08-03 5:33 ` Avi Kivity
2010-08-02 22:25 ` Anthony Liguori
2010-08-02 22:54 ` Andre Przywara
2010-08-02 23:40 ` Anthony Liguori
2010-08-03 5:41 ` Avi Kivity
2010-08-02 13:49 ` Ulrich Drepper
2010-08-02 18:38 ` Ricardo Martins
2010-08-02 22:24 ` Andre Przywara
2010-08-02 22:15 ` Andre Przywara
2010-08-02 22:23 ` Anthony Liguori
2010-08-02 22:42 ` Andre Przywara
2010-08-02 23:36 ` Anthony Liguori
2010-08-03 6:25 ` Dor Laor
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=4C574512.6030903@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=andre.przywara@amd.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ricardo.martins.br@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