From: "Filip Navara" <xnavara@volny.cz>
To: Thiemo Seufer <ths@networkno.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Intel cache info
Date: Tue, 11 Sep 2007 09:20:04 +0200 [thread overview]
Message-ID: <5b31733c0709110020x690f6b65v442d2f5f797b5968@mail.gmail.com> (raw)
In-Reply-To: <20070909150415.GA10713@networkno.de>
[-- Attachment #1.1: Type: text/plain, Size: 600 bytes --]
Here it is, sorry for the delay.
Best regards,
Filip Navara
On 9/9/07, Thiemo Seufer <ths@networkno.de> wrote:
>
> Filip Navara wrote:
> > Fix the CPUID function 2 to correctly report cache info for the
> particular
> > processor. I chose the values closest to the ones reported in the AMD
> > registers. This is important for operating systems that detect cache
> line
> > width and later call CLFLUSH for each line. In the previous
> implementation
> > the values didn't specify L2 cache line width and so Darwin endlessly
> looped
> > trying to flush them.
>
> No patch attached.
>
>
> Thiemo
>
[-- Attachment #1.2: Type: text/html, Size: 909 bytes --]
[-- Attachment #2: qemu-cache-info.patch --]
[-- Type: application/octet-stream, Size: 637 bytes --]
Index: target-i386/helper.c
===================================================================
RCS file: /sources/qemu/qemu/target-i386/helper.c,v
retrieving revision 1.84
diff -u -r1.84 helper.c
--- target-i386/helper.c 26 Jun 2007 08:35:18 -0000 1.84
+++ target-i386/helper.c 8 Sep 2007 16:07:23 -0000
@@ -1657,10 +1657,10 @@
break;
case 2:
/* cache info: needed for Pentium Pro compatibility */
- EAX = 0x410601;
+ EAX = 1;
EBX = 0;
ECX = 0;
- EDX = 0;
+ EDX = 0x2c307d;
break;
case 0x80000000:
EAX = env->cpuid_xlevel;
prev parent reply other threads:[~2007-09-11 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 19:27 [Qemu-devel] [PATCH] Intel cache info Filip Navara
2007-09-09 13:47 ` Dan Kenigsberg
2007-09-09 15:04 ` Thiemo Seufer
2007-09-11 7:20 ` Filip Navara [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=5b31733c0709110020x690f6b65v442d2f5f797b5968@mail.gmail.com \
--to=xnavara@volny.cz \
--cc=qemu-devel@nongnu.org \
--cc=ths@networkno.de \
/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).