From: Avi Kivity <avi@qumranet.com>
To: Glauber Costa <gcosta@redhat.com>
Cc: kvm-devel@lists.sourceforge.net,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] fixup 3dnow! support
Date: Wed, 07 May 2008 11:13:01 +0300 [thread overview]
Message-ID: <4821648D.2090706@qumranet.com> (raw)
In-Reply-To: <12100912622893-git-send-email-gcosta@redhat.com>
Glauber Costa wrote:
> qemu recently added support for 3dnow instructions. Because of
> that, 3dnow will be featured among cpuid bits. But this will
> break kvm in cpus that don't have those instructions (which includes
> my laptop). So we fixup our cpuid before exposing it to the guest.
>
>
I've already fixed this in userspace.
In general I don't like silently modifying cpuid options in the kernel,
since that means we cannot be confident as to what the cpuid the guest
sees actually is, and so we can't be sure that migration will succeed.
Instead, the preferred path is to query what cpuid bits the host
support, pass that to the management app in order to compute the
greatest common subset, and tell the kernel to use that set.
nx is handled differently due to compatibility issues. In time we can
remove the special handling.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
prev parent reply other threads:[~2008-05-07 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 16:27 [PATCH] fixup 3dnow! support Glauber Costa
2008-05-06 23:05 ` Alexander Graf
2008-05-06 23:08 ` Glauber Costa
2008-05-07 8:19 ` Avi Kivity
2008-05-07 9:39 ` Alexander Graf
2008-05-07 8:13 ` 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=4821648D.2090706@qumranet.com \
--to=avi@qumranet.com \
--cc=gcosta@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=virtualization@lists.linux-foundation.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