qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] introduce kvm64 CPU
Date: Sun, 23 Aug 2009 12:05:13 +0300	[thread overview]
Message-ID: <4A910649.5000600@redhat.com> (raw)
In-Reply-To: <4A8F18CB.6000200@amd.com>

On 08/22/2009 12:59 AM, Andre Przywara wrote:
>> Typically users will want more specialized greatest common denomiator 
>> cpu types; if a site has standardized on recent hardware they will 
>> want the features of that hardware exposed.
> Sure, but this was not the purpose of this patch. Currently KVM guests 
> see a CPU type which is TCG dependent, so I just wanted to get rid of 
> this. Features of TCG and features of the host processor are totally 
> uncorrelated. This new type should be KVM's default, leaving -cpu host 
> as the alternative for the non-migration case.

That does make sense.  Note we can call it '-cpu kvm' since qemu will 
strip away long mode if it is not supported by the cpu or by the kernel.

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

  reply	other threads:[~2009-08-23  9:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20 21:34 [Qemu-devel] [PATCH] introduce kvm64 CPU Andre Przywara
2009-08-21 13:33 ` [Qemu-devel] " Jamie Lokier
2009-08-21 14:23   ` Andre Przywara
2009-08-22  1:45     ` Jamie Lokier
2009-08-21 15:41 ` Avi Kivity
2009-08-21 16:01   ` Glauber Costa
2009-08-21 21:53     ` Andre Przywara
2009-08-23  9:03       ` Avi Kivity
2009-08-23 13:20       ` Amit Shah
2009-08-21 21:59   ` Andre Przywara
2009-08-23  9:05     ` Avi Kivity [this message]
2009-08-23 12:47       ` Jamie Lokier
2009-08-22  1:03   ` Jamie Lokier

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=4A910649.5000600@redhat.com \
    --to=avi@redhat.com \
    --cc=andre.przywara@amd.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 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).