From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: anthony@codemonkey.ws, qemu-devel@nongnu.org,
kvm@vger.kernel.org, jamie@shareable.org
Subject: Re: [PATCH] introduce kvm64 CPU
Date: Fri, 21 Aug 2009 18:41:49 +0300 [thread overview]
Message-ID: <4A8EC03D.4000202@redhat.com> (raw)
In-Reply-To: <1250804057-29681-1-git-send-email-andre.przywara@amd.com>
On 08/21/2009 12:34 AM, Andre Przywara wrote:
> In addition to the TCG based qemu64 type let's introduce a kvm64 CPU type,
> which is the least common denominator of all KVM-capable x86-CPUs
> (based on Intel Pentium 4 Prescott). It can be used as a base type
> for migration.
>
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.
I think this is best left to management software, which has more
information about the migration pool.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
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: Fri, 21 Aug 2009 18:41:49 +0300 [thread overview]
Message-ID: <4A8EC03D.4000202@redhat.com> (raw)
In-Reply-To: <1250804057-29681-1-git-send-email-andre.przywara@amd.com>
On 08/21/2009 12:34 AM, Andre Przywara wrote:
> In addition to the TCG based qemu64 type let's introduce a kvm64 CPU type,
> which is the least common denominator of all KVM-capable x86-CPUs
> (based on Intel Pentium 4 Prescott). It can be used as a base type
> for migration.
>
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.
I think this is best left to management software, which has more
information about the migration pool.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-08-21 15:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 21:34 [PATCH] introduce kvm64 CPU Andre Przywara
2009-08-20 21:34 ` [Qemu-devel] " Andre Przywara
2009-08-21 13:33 ` Jamie Lokier
2009-08-21 13:33 ` [Qemu-devel] " Jamie Lokier
2009-08-21 14:23 ` Andre Przywara
2009-08-21 14:23 ` [Qemu-devel] " Andre Przywara
2009-08-22 1:45 ` Jamie Lokier
2009-08-22 1:45 ` [Qemu-devel] " Jamie Lokier
2009-08-21 15:41 ` Avi Kivity [this message]
2009-08-21 15:41 ` Avi Kivity
2009-08-21 16:01 ` Glauber Costa
2009-08-21 16:01 ` [Qemu-devel] " Glauber Costa
2009-08-21 21:53 ` Andre Przywara
2009-08-21 21:53 ` [Qemu-devel] " Andre Przywara
2009-08-23 9:03 ` Avi Kivity
2009-08-23 9:03 ` [Qemu-devel] " Avi Kivity
2009-08-23 13:20 ` Amit Shah
2009-08-23 13:20 ` [Qemu-devel] " Amit Shah
2009-08-21 21:59 ` Andre Przywara
2009-08-21 21:59 ` [Qemu-devel] " Andre Przywara
2009-08-23 9:05 ` Avi Kivity
2009-08-23 9:05 ` [Qemu-devel] " Avi Kivity
2009-08-23 12:47 ` Jamie Lokier
2009-08-23 12:47 ` [Qemu-devel] " Jamie Lokier
2009-08-22 1:03 ` Jamie Lokier
2009-08-22 1:03 ` [Qemu-devel] " 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=4A8EC03D.4000202@redhat.com \
--to=avi@redhat.com \
--cc=andre.przywara@amd.com \
--cc=anthony@codemonkey.ws \
--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.