From: Andre Przywara <andre.przywara@amd.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] omit 3DNOW! CPUID bits from qemu64 CPU model
Date: Thu, 16 Jul 2009 23:09:02 +0200 [thread overview]
Message-ID: <4A5F96EE.30206@amd.com> (raw)
In-Reply-To: <B1CF1BFF-52DB-4142-BE60-4316FEA22E3D@suse.de>
Alexander Graf wrote:
>
> On 16.07.2009, at 14:49, Andre Przywara wrote:
>
>> Since we recently do not disable 3DNOW! support anymore, we should
>> avoid setting the bits in the default qemu64 CPU model to ease
>> migration. TCG does not support it anyway and even AMD deprecates
>> it's usage nowadays.
>
> TCG does not implement it but it was enabled in the qemu64 type? That
> sounds like a serious bug people would have found before.
Yes, it was enabled in the qemu64 type since "the dawn of time". But at
the same moment it was unconditionally (both for TCG and KVM) masked out
later, so there were no 3DNOW bits at any time. Commit 671e4676 changed
that to be only applicable to TCG. So in the last three weeks or so by
default there were 3DNOW bits in KVM on AMD processors.
This is a particular problem with DirectX9 (WindowsXP), which still uses
3DNow if available.
> I really think we should try and keep the "qemu64" type (TCG
> capabilities) and the "kvm safe" type separate. IMHO the best scenario
> would be a -cpu "safe" type, used as default, that is the common
> dominator between KVM on VMX, KVM on SVM and TCG.
Well, I'd like to leave TCG out of the migration theme by default. If
you seriously use KVM and migration, I suppose TCG is not an option for
you. It's a nice thing to have, but for different things than KVM.
But I will check how much difference there is between Prescott-2M,
K8RevF and TCG, maybe we can leave it in.
Regards,
Andre.
>
> That would also make it easier to know where to put other fancy features
> like "SVM" :-).
>
> Alex
>
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 488-3567-12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Jochen Polster; Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
prev parent reply other threads:[~2009-07-16 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 12:49 [Qemu-devel] [PATCH] omit 3DNOW! CPUID bits from qemu64 CPU model Andre Przywara
2009-07-16 13:38 ` Alexander Graf
2009-07-16 16:01 ` Jamie Lokier
2009-07-16 16:08 ` Alexander Graf
2009-07-16 16:36 ` Jamie Lokier
2009-07-16 16:50 ` Alexander Graf
2009-07-16 21:09 ` Andre Przywara [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=4A5F96EE.30206@amd.com \
--to=andre.przywara@amd.com \
--cc=agraf@suse.de \
--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).