qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	Ryan Harper <ryanh@us.ibm.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>,
	KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH v2 2/3] KVM: Use -cpu best as default on x86
Date: Mon, 02 Jul 2012 17:27:04 +0300	[thread overview]
Message-ID: <4FF1AFB8.3090904@redhat.com> (raw)
In-Reply-To: <1340728795-4379-2-git-send-email-agraf@suse.de>

On 06/26/2012 07:39 PM, Alexander Graf wrote:
> 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".
> 
> That's a really good default when using TCG, but when running with KVM
> we much rather want a default saying "the maximum performance I can get".
> 
> Fortunately we just added an option that gives us the best performance
> while still staying safe on the testability side of things: -cpu best.
> So all we need to do is make -cpu best the default when the user doesn't
> explicitly specify a CPU type.
> 
> This fixes a lot of subtile breakage in the GNU toolchain (libgmp) which

subtle

> hicks up on QEMU's non-existent CPU models.
> 
> This patch also adds a new pc-1.2 machine type to stay backwards compatible
> with older versions of QEMU.

-- 
error compiling committee.c: too many arguments to function

      parent reply	other threads:[~2012-07-02 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1340728795-4379-1-git-send-email-agraf@suse.de>
2012-07-02 14:02 ` [Qemu-devel] [PATCH v2 1/3] KVM: Add new -cpu best Alexander Graf
2012-07-02 14:24 ` Andreas Färber
2012-07-02 14:25 ` Avi Kivity
2012-07-09 11:57   ` Alexander Graf
     [not found] ` <1340728795-4379-2-git-send-email-agraf@suse.de>
2012-07-02 14:27   ` Avi Kivity [this message]

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=4FF1AFB8.3090904@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ryanh@us.ibm.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).