All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Jamie Lokier <jamie@shareable.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] KVMs default CPU type
Date: Thu, 25 Jun 2009 11:29:15 +0300	[thread overview]
Message-ID: <4A43355B.4080406@redhat.com> (raw)
In-Reply-To: <4A43314E.5050500@amd.com>

On 06/25/2009 11:11 AM, Andre Przywara wrote:
> I think we should go away from using qemu64 as a default for KVM. In 
> my opinion we should target -cpu host as KVM's default, while in 
> parallel create a -cpu migrate type (still fiddling with the CPUID 
> details of that), which takes over the qemu64 role of being some kind 
> of least common denominator. This should be a family 15 CPU (AMD K8 or 
> Intel P4) with a constant vendor ID (in my experiments Intel showed 
> less problems with guests). Since 64bit Windows has a whitelist of 
> known vendor IDs (AMD, Intel on XP, additionally Via on Win7) we 
> cannot use a bogus vendor, although this should impose the least 
> problems.

-cpu host may have issues other than migration; for example if you 
upgrade your host processor guests will notice and perhaps trigger a 
revalidation.  It also means every host offers something slightly 
different to guests, increasing the test matrix.

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


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] KVMs default CPU type
Date: Thu, 25 Jun 2009 11:29:15 +0300	[thread overview]
Message-ID: <4A43355B.4080406@redhat.com> (raw)
In-Reply-To: <4A43314E.5050500@amd.com>

On 06/25/2009 11:11 AM, Andre Przywara wrote:
> I think we should go away from using qemu64 as a default for KVM. In 
> my opinion we should target -cpu host as KVM's default, while in 
> parallel create a -cpu migrate type (still fiddling with the CPUID 
> details of that), which takes over the qemu64 role of being some kind 
> of least common denominator. This should be a family 15 CPU (AMD K8 or 
> Intel P4) with a constant vendor ID (in my experiments Intel showed 
> less problems with guests). Since 64bit Windows has a whitelist of 
> known vendor IDs (AMD, Intel on XP, additionally Via on Win7) we 
> cannot use a bogus vendor, although this should impose the least 
> problems.

-cpu host may have issues other than migration; for example if you 
upgrade your host processor guests will notice and perhaps trigger a 
revalidation.  It also means every host offers something slightly 
different to guests, increasing the test matrix.

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

  reply	other threads:[~2009-06-25  8:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 16:21 [Qemu-devel] allow sysenter on 32bit guests running on vmx host Andrea Arcangeli
2009-06-24 17:29 ` Jamie Lokier
2009-06-24 17:48   ` Filip Navara
2009-06-24 21:13     ` Andrea Arcangeli
2009-06-24 21:12   ` Andrea Arcangeli
2009-06-24 21:39     ` Jamie Lokier
2009-06-24 22:32       ` Andrea Arcangeli
2009-06-25  8:11       ` [Qemu-devel] KVMs default CPU type (was: allow sysenter on 32bit guests running on vmx host) Andre Przywara
2009-06-25  8:29         ` Avi Kivity [this message]
2009-06-25  8:29           ` [Qemu-devel] KVMs default CPU type Avi Kivity
2009-06-26  0:42         ` [Qemu-devel] KVMs default CPU type (was: allow sysenter on 32bit guests running on vmx host) Andrea Arcangeli
2009-06-26  0:42           ` Andrea Arcangeli
2009-06-26  1:06           ` Andrea Arcangeli
2009-06-26  1:06             ` Andrea Arcangeli
2009-06-25 17:39       ` [Qemu-devel] allow sysenter on 32bit guests running on vmx host Paul Brook
2009-06-25 21:02         ` Andrea Arcangeli
2009-06-25 22:12           ` Paul Brook
2009-06-25 23:27             ` Andrea Arcangeli
2009-06-25 23:49               ` Paul Brook
2009-06-26  0:06                 ` Andrea Arcangeli

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=4A43355B.4080406@redhat.com \
    --to=avi@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=andre.przywara@amd.com \
    --cc=jamie@shareable.org \
    --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.