All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Ryan Harper <ryanh@us.ibm.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	kvm list <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH 2/2] KVM: Use -cpu best as default on x86
Date: Mon, 16 Jan 2012 13:46:57 -0600	[thread overview]
Message-ID: <20120116194657.GD25198@us.ibm.com> (raw)
In-Reply-To: <47E08DA5-61EF-4DF8-AB22-E1BF42807602@suse.de>

* Alexander Graf <agraf@suse.de> [2012-01-16 13:37]:
> 
> On 16.01.2012, at 20:30, Ryan Harper wrote:
> 
> > * Alexander Graf <agraf@suse.de> [2012-01-08 17:53]:
> >> When running QEMU without -cpu parameter, the user usually wants a sane
> >> default. So far, we're using the qemu64/qemu32 CPU type, which basically
> >> means "the maximum TCG can emulate".
> > 
> > it also means we all maximum possible migration targets.  Have you
> > given any thought to migration with -cpu best? 
> 
> If you have the same boxes in your cluster, migration just works. If
> you don't, you usually use a specific CPU model that is the least
> dominator between your boxes either way.

Sure, but the idea behind -cpu best is to not have to figure that out;
you had suggested that the qemu64/qemu32 were just related to TCG, and
what I'm suggesting is that it's also the most compatible w.r.t
migration.  

it sounds like if migration is a requirement, then -cpu best probably
isn't something that would be used.  I suppose I'm OK with that, or at
least I don't have a better suggestion on how to carefully push up the
capabilities without at some point breaking migration.

> 
> The current kvm64 type is broken. Libgmp just abort()s when we pass it
> in. So anything is better than what we do today on AMD hosts :).

I wonder if it breaks with Cyris cpus... other tools tend to do runtime
detection (mplayer).


> 
> 
> Alex

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com

WARNING: multiple messages have this Message-ID (diff)
From: Ryan Harper <ryanh@us.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Ryan Harper <ryanh@us.ibm.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	kvm list <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] KVM: Use -cpu best as default on x86
Date: Mon, 16 Jan 2012 13:46:57 -0600	[thread overview]
Message-ID: <20120116194657.GD25198@us.ibm.com> (raw)
In-Reply-To: <47E08DA5-61EF-4DF8-AB22-E1BF42807602@suse.de>

* Alexander Graf <agraf@suse.de> [2012-01-16 13:37]:
> 
> On 16.01.2012, at 20:30, Ryan Harper wrote:
> 
> > * Alexander Graf <agraf@suse.de> [2012-01-08 17:53]:
> >> When running QEMU without -cpu parameter, the user usually wants a sane
> >> default. So far, we're using the qemu64/qemu32 CPU type, which basically
> >> means "the maximum TCG can emulate".
> > 
> > it also means we all maximum possible migration targets.  Have you
> > given any thought to migration with -cpu best? 
> 
> If you have the same boxes in your cluster, migration just works. If
> you don't, you usually use a specific CPU model that is the least
> dominator between your boxes either way.

Sure, but the idea behind -cpu best is to not have to figure that out;
you had suggested that the qemu64/qemu32 were just related to TCG, and
what I'm suggesting is that it's also the most compatible w.r.t
migration.  

it sounds like if migration is a requirement, then -cpu best probably
isn't something that would be used.  I suppose I'm OK with that, or at
least I don't have a better suggestion on how to carefully push up the
capabilities without at some point breaking migration.

> 
> The current kvm64 type is broken. Libgmp just abort()s when we pass it
> in. So anything is better than what we do today on AMD hosts :).

I wonder if it breaks with Cyris cpus... other tools tend to do runtime
detection (mplayer).


> 
> 
> Alex

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com

  reply	other threads:[~2012-01-16 19:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08 23:52 [PATCH 1/2] KVM: Add new -cpu best Alexander Graf
2012-01-08 23:52 ` [Qemu-devel] " Alexander Graf
2012-01-08 23:52 ` [PATCH 2/2] KVM: Use -cpu best as default on x86 Alexander Graf
2012-01-08 23:52   ` [Qemu-devel] " Alexander Graf
2012-01-16 19:30   ` Ryan Harper
2012-01-16 19:30     ` [Qemu-devel] " Ryan Harper
2012-01-16 19:36     ` Alexander Graf
2012-01-16 19:36       ` Alexander Graf
2012-01-16 19:46       ` Ryan Harper [this message]
2012-01-16 19:46         ` Ryan Harper
2012-01-16 19:51         ` Alexander Graf
2012-01-16 19:51           ` Alexander Graf
2012-01-16 20:13           ` Ryan Harper
2012-01-16 20:13             ` [Qemu-devel] " Ryan Harper
2012-01-16 20:51             ` Alexander Graf
2012-01-16 21:33               ` Ryan Harper
2012-01-09  0:02 ` [Qemu-devel] [PATCH 1/2] KVM: Add new -cpu best Peter Maydell
2012-01-09  0:02   ` Peter Maydell
2012-01-09  0:06   ` Alexander Graf
2012-01-09  0:06     ` Alexander Graf
2012-01-16 19:33 ` Anthony Liguori
2012-01-16 19:33   ` Anthony Liguori
2012-01-16 19:42   ` Alexander Graf
2012-01-16 19:42     ` Alexander Graf

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=20120116194657.GD25198@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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 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.