From: "Filip Navara" <xnavara@volny.cz>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] CPUID xlevel
Date: Sat, 8 Sep 2007 21:29:20 +0200 [thread overview]
Message-ID: <5b31733c0709081229h157b427pb3256dcffe3d46f3@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 108 bytes --]
Fix the reported xlevel for Intel CPU. We support the extended CPUID calls,
so report that we support them.
[-- Attachment #1.2: Type: text/html, Size: 112 bytes --]
[-- Attachment #2: qemu-cpuid-xlevel.patch --]
[-- Type: application/octet-stream, Size: 736 bytes --]
Index: target-i386/helper2.c
===================================================================
RCS file: /sources/qemu/qemu/target-i386/helper2.c,v
retrieving revision 1.48
diff -u -r1.48 helper2.c
--- target-i386/helper2.c 31 Jul 2007 23:09:18 -0000 1.48
+++ target-i386/helper2.c 6 Sep 2007 17:06:34 -0000
@@ -114,7 +114,7 @@
env->cpuid_ext_features = CPUID_EXT_SSE3;
env->cpuid_features |= CPUID_FXSR | CPUID_MMX | CPUID_SSE | CPUID_SSE2 | CPUID_PAE | CPUID_SEP;
env->cpuid_features |= CPUID_APIC;
- env->cpuid_xlevel = 0;
+ env->cpuid_xlevel = 0x80000006;
{
const char *model_id = "QEMU Virtual CPU version " QEMU_VERSION;
int c, len, i;
reply other threads:[~2007-09-08 19:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5b31733c0709081229h157b427pb3256dcffe3d46f3@mail.gmail.com \
--to=xnavara@volny.cz \
--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).