From: Bernhard Kauer <kauer@os.inf.tu-dresden.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] SVM enabled processor should provide cpuid Fn8000_000A
Date: Tue, 18 Dec 2007 14:01:52 +0100 [thread overview]
Message-ID: <20071218130152.GB3301@chrom.inf.tu-dresden.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 163 bytes --]
An SVM enabled processor should provide the CPUID extended leaf Fn8000_000A
(see AMD documentation #25481). The attached patch add this feature.
Bernhard Kauer
[-- Attachment #2: qemu_cpuid.diff --]
[-- Type: text/x-diff, Size: 1142 bytes --]
Index: target-i386/helper.c
===================================================================
RCS file: /sources/qemu/qemu/target-i386/helper.c,v
retrieving revision 1.97
diff -u -r1.97 helper.c
--- target-i386/helper.c 9 Dec 2007 23:39:22 -0000 1.97
+++ target-i386/helper.c 18 Dec 2007 12:40:06 -0000
@@ -1751,6 +1819,12 @@
ECX = 0;
EDX = 0;
break;
+ case 0x8000000A:
+ EAX = 0x00000001;
+ EBX = 0;
+ ECX = 0;
+ EDX = 0;
+ break;
default:
/* reserved values: zero */
EAX = 0;
Index: target-i386/helper2.c
===================================================================
RCS file: /sources/qemu/qemu/target-i386/helper2.c,v
retrieving revision 1.60
diff -u -r1.60 helper2.c
--- target-i386/helper2.c 9 Dec 2007 02:43:19 -0000 1.60
+++ target-i386/helper2.c 18 Dec 2007 12:40:06 -0000
@@ -150,7 +150,7 @@
.ext2_features = (PPRO_FEATURES & 0x0183F3FF) |
CPUID_EXT2_LM | CPUID_EXT2_SYSCALL | CPUID_EXT2_NX,
.ext3_features = CPUID_EXT3_SVM,
- .xlevel = 0x80000008,
+ .xlevel = 0x8000000A,
},
#endif
{
next reply other threads:[~2007-12-18 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 13:01 Bernhard Kauer [this message]
2007-12-24 12:08 ` [Qemu-devel] [PATCH] SVM enabled processor should provide cpuid Fn8000_000A Alexander Graf
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=20071218130152.GB3301@chrom.inf.tu-dresden.de \
--to=kauer@os.inf.tu-dresden.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).