From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Marcelo Tosatti" <mtosatti@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
"Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [patch 2/2] target-i386: block migration and savevm if invariant tsc is exposed
Date: Tue, 29 Apr 2014 08:22:36 +0200 [thread overview]
Message-ID: <535F452C.1050302@redhat.com> (raw)
In-Reply-To: <20140428192337.GA3363@otherpad.lan.raisama.net>
Il 28/04/2014 21:23, Eduardo Habkost ha scritto:
> > Makes sense. Basically "-cpu host,migratable=yes" is close to
> > libvirt's host-model and Alex Graf's proposed "-cpu best". Should we
> > call it "-cpu best" and drop migratability of "-cpu host"?
>
> "-cpu best" is different from the modes above. It means "use the best
> existing CPU model (from the pre-defined table) that can run on this
> host".
Yes, it's not exactly the same. In practice the behavior should be close.
> And it would have the same ambiguities we found on "-cpu host": if a CPU
> model in the table have invtsc enabled, should it be considered a
> candidate for "-cpu best", or not?
No CPU model in the table should have invtsc enabled. :)
Paolo
next prev parent reply other threads:[~2014-04-29 6:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 19:10 [patch 0/2] expose invariant tsc flag for kvm guests Marcelo Tosatti
2014-04-22 19:10 ` [patch 1/2] target-i386: support "invariant tsc" flag Marcelo Tosatti
2014-04-23 0:26 ` Paolo Bonzini
2014-04-23 1:11 ` Eduardo Habkost
2014-04-22 19:10 ` [patch 2/2] target-i386: block migration and savevm if invariant tsc is exposed Marcelo Tosatti
2014-04-22 19:28 ` Marcelo Tosatti
2014-04-22 20:38 ` Eduardo Habkost
2014-04-22 21:27 ` Marcelo Tosatti
2014-04-23 1:14 ` Eduardo Habkost
2014-04-24 20:42 ` Paolo Bonzini
2014-04-24 20:57 ` Eduardo Habkost
2014-04-24 22:57 ` Paolo Bonzini
2014-04-24 23:18 ` Eduardo Habkost
2014-04-25 21:08 ` Paolo Bonzini
2014-04-28 15:46 ` Eduardo Habkost
2014-04-28 19:06 ` Paolo Bonzini
2014-04-28 19:23 ` Eduardo Habkost
2014-04-29 6:22 ` Paolo Bonzini [this message]
2014-04-29 14:29 ` Eduardo Habkost
2014-04-23 18:20 ` [patch 0/2] expose invariant tsc flag for kvm guests (v2) Marcelo Tosatti
2014-04-23 18:20 ` [patch 1/2] target-i386: support "invariant tsc" flag Marcelo Tosatti
2014-04-23 19:04 ` Eduardo Habkost
2014-04-23 18:20 ` [patch 2/2] target-i386: block migration and savevm if invariant tsc is exposed Marcelo Tosatti
2014-04-23 19:09 ` Eduardo Habkost
2014-04-23 21:04 ` target-i386: block migration and savevm if invariant tsc is exposed (v3) Marcelo Tosatti
2014-04-24 19:21 ` Eduardo Habkost
2014-04-24 21:32 ` Marcelo Tosatti
2014-04-25 20:38 ` Eduardo Habkost
2014-04-25 22:47 ` [PATCH] savevm: check vmsd for migratability status Marcelo Tosatti
2014-04-28 20:36 ` Eduardo Habkost
2014-04-30 0:39 ` [PATCH] savevm: check vmsd for migratability status (v2) Marcelo Tosatti
2014-04-30 15:47 ` [Qemu-devel] " Eduardo Habkost
2014-04-25 22:47 ` target-i386: block migration and savevm if invariant tsc is exposed (v3) Marcelo Tosatti
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=535F452C.1050302@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
/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