All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Avi Kivity <avi@redhat.com>,
	Ricardo Martins <ricardo.martins.br@gmail.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM Processor cache size
Date: Tue, 3 Aug 2010 00:35:49 +0200	[thread overview]
Message-ID: <4C574845.8060906@amd.com> (raw)
In-Reply-To: <4C574512.6030903@codemonkey.ws>

Anthony Liguori wrote:
> 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.
You are right. I am sorry if that created a misunderstanding, I actually 
meant: "was not committed".
> 
> 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.
Would you accept a patch simply disabling migration in case -cpu host 
was used in the first place?
> 
> 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.
Is there already a way to communicate from the target to the source? 
This would allow to check for migrate-ability before we transfer any 
data. Or should we handle this in a management application?

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 488-3567-12


  reply	other threads:[~2010-08-02 22:35 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
2010-08-02 22:35       ` Andre Przywara [this message]
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=4C574845.8060906@amd.com \
    --to=andre.przywara@amd.com \
    --cc=anthony@codemonkey.ws \
    --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 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.