From: Glauber Costa <gcosta@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
Avi Kivity <avi@qumranet.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] fixup 3dnow! support
Date: Tue, 06 May 2008 20:08:39 -0300 [thread overview]
Message-ID: <4820E4F7.9000606@redhat.com> (raw)
In-Reply-To: <6CF4ABCF-B131-41E0-AAFE-2928E01DDAAF@suse.de>
Alexander Graf wrote:
>
> On May 6, 2008, at 6:27 PM, 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 actually don't see where the problem is here. As far as I read the
> code, the CPUID feature function gets received from the host CPU and
> bitwise ANDed with a bunch of features that are known to work. What's
> wrong with that approach?
Probably is that besides that known to work features, there are also
features that qemu puts in unconditionally. Among them, 3DNOW.
> But I'm pretty sure Dao can tell us a lot more about this.
Sure, it would be welcome.
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2008-05-06 23:08 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 [this message]
2008-05-07 8:19 ` Avi Kivity
2008-05-07 9:39 ` Alexander Graf
2008-05-07 8:13 ` Avi Kivity
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=4820E4F7.9000606@redhat.com \
--to=gcosta@redhat.com \
--cc=agraf@suse.de \
--cc=avi@qumranet.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