From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Make CPUID 4 work again
Date: Thu, 18 Dec 2008 12:13:39 +0100 [thread overview]
Message-ID: <494A3063.6070302@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
The recent split of the CPUID helper function broke CPUID 4, which
relies on ECX information.
This patch writes ECX into the ecx variable, which is used by
cpu_x86_cpuid to enumerate the current index.
Using this patch booting Linux with -cpu core2duo works again.
Signed-off-by: Alexander Graf <agraf@suse.de>
[-- Attachment #2: qemu-cpuid4.patch --]
[-- Type: text/x-patch, Size: 382 bytes --]
Index: target-i386/op_helper.c
===================================================================
--- target-i386/op_helper.c (revision 6082)
+++ target-i386/op_helper.c (working copy)
@@ -1898,6 +1898,7 @@
helper_svm_check_intercept_param(SVM_EXIT_CPUID, 0);
+ ecx = ECX;
cpu_x86_cpuid(env, (uint32_t)EAX, &eax, &ebx, &ecx, &edx);
EAX = eax;
EBX = ebx;
reply other threads:[~2008-12-18 11:13 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=494A3063.6070302@suse.de \
--to=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).