From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: "Przywara, Andre" <Andre.Przywara@amd.com>,
Arnd Bergmann <arnd@arndb.de>, KVM list <kvm@vger.kernel.org>,
john cooper <john.cooper@redhat.com>,
dlaor@redhat.com, qemu-devel@nongnu.org,
Chris Wright <chrisw@sous-sol.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Add definitions for current cpu models..
Date: Thu, 28 Jan 2010 08:10:15 -0600 [thread overview]
Message-ID: <4B619AC7.7010705@codemonkey.ws> (raw)
In-Reply-To: <1D6BE1B1-FCA1-4022-A98C-990A369F6E59@suse.de>
On 01/28/2010 02:43 AM, Alexander Graf wrote:
> On 28.01.2010, at 09:19, Arnd Bergmann wrote:
>
>
>> On Monday 25 January 2010, Dor Laor wrote:
>>
>>> x86 qemu64
>>> x86 phenom
>>> x86 core2duo
>>> x86 kvm64
>>> x86 qemu32
>>> x86 coreduo
>>> x86 486
>>> x86 pentium
>>> x86 pentium2
>>> x86 pentium3
>>> x86 athlon
>>> x86 n270
>>>
>> I think a really nice addition would be an autodetect option for those
>> users (e.g. desktop) that know they do not want to migrate the guest
>> to a lower-spec machine.
>>
>> That option IMHO should just show up as identical to the host cpu, with
>> the exception of features that are not supported in the guest.
>>
> That's exactly what -cpu host is. IIRC it's the default now.
>
Not yet. Someone has to send a patch.
We can't enforce this wrt migration until someone implements migration
of cpuid state.
Regards,
Anthony Liguori
> Alex
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-01-28 14:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 16:45 [Qemu-devel] [PATCH] Add definitions for current cpu models john cooper
2010-01-19 19:39 ` Anthony Liguori
2010-01-19 20:03 ` Chris Wright
2010-01-19 22:12 ` Jamie Lokier
2010-01-19 22:20 ` Chris Wright
2010-01-19 22:25 ` Anthony Liguori
2010-01-20 0:15 ` Chris Wright
2010-01-20 14:21 ` Anthony Liguori
2010-01-20 14:27 ` Gleb Natapov
2010-01-20 1:38 ` Jamie Lokier
2010-01-20 20:09 ` john cooper
2010-01-20 20:26 ` Daniel P. Berrange
2010-01-20 20:53 ` Anthony Liguori
2010-01-21 0:25 ` Chris Wright
2010-01-21 1:18 ` john cooper
2010-01-21 14:39 ` Andre Przywara
2010-01-21 17:06 ` Blue Swirl
2010-01-21 15:05 ` Anthony Liguori
2010-01-21 16:43 ` john cooper
2010-01-21 18:59 ` Anthony Liguori
2010-01-25 9:08 ` Dor Laor
2010-01-25 11:27 ` Jamie Lokier
2010-01-25 14:21 ` Anthony Liguori
2010-01-25 22:35 ` Dor Laor
2010-01-26 8:26 ` Gerd Hoffmann
2010-01-26 12:54 ` Anthony Liguori
2010-01-28 8:19 ` Arnd Bergmann
2010-01-28 8:43 ` Alexander Graf
2010-01-28 10:09 ` Arnd Bergmann
2010-01-28 14:10 ` Anthony Liguori [this message]
2010-01-19 22:11 ` Jamie Lokier
2010-01-20 20:09 ` john cooper
2010-01-21 17:50 ` Jamie Lokier
2010-01-21 18:13 ` Jamie Lokier
2010-01-21 18:36 ` john cooper
2010-01-19 22:15 ` Jamie Lokier
2010-01-20 20:11 ` john cooper
2010-01-21 17:55 ` Jamie Lokier
2010-01-21 18:34 ` john cooper
2010-01-20 23:20 ` [Qemu-devel] " Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2009-12-21 6:46 [Qemu-devel] " john cooper
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=4B619AC7.7010705@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Andre.Przywara@amd.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=chrisw@sous-sol.org \
--cc=dlaor@redhat.com \
--cc=john.cooper@redhat.com \
--cc=kraxel@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 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).