From: ace <acelists@atlas.sk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] couid for x86 CPUs
Date: Tue, 15 Nov 2005 21:29:43 +0100 [thread overview]
Message-ID: <437A4537.5080100@atlas.sk> (raw)
In-Reply-To: <43786AED.7090402@os.inf.tu-dresden.de>
Can you test this with and without kqemu?
When I tested this last, the result of cpuid (and other CPU probing
operations) were differing in these 2 scenarios. Without kqemu, qemu
emulates a P II. With kqemu, some programs are able to find out the real
CPU on the host system.
Peter
Ronald Aigner wrote:
> Hi,
> Version 0.7.2 from the Website returns invalid cache size for the i386
> architecture.
> Currently the 'cpuid' instruction with eax==1 returns a processor ID of
> 0x633 that is an "Intel Pentium II (Klamath)". The Klamath is specified
> with 512kB of L2 Cache (see
> http://www.pcguide.com/ref/cpu/fam/g6PII-c.html).
> However the 'cpuid' instruction with eax==2 returns a descriptor value
> of 0x41, which indicates 128kB of L2 Cache (see
> http://faydoc.tripod.com/cpu/cpuid.htm). The correct value should be 0x43.
> To fix this, line 1317 in file target-i386/helper.c should read:
> EAX = 0x430601;
>
> Thanks, Ron.
>
> PS: A hint on the website on where to post bug-reports would be helpful.
>
> PPS: Please include me into reply. I'm not subscribed to the list.
> --
> Mit freundlichen Gruessen / with regards
> ra3 @ inf.tu-dresden.de
> http://os.inf.tu-dresden.de/~ra3/
_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
prev parent reply other threads:[~2005-11-15 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 10:46 [Qemu-devel] couid for x86 CPUs Ronald Aigner
2005-11-15 20:29 ` ace [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=437A4537.5080100@atlas.sk \
--to=acelists@atlas.sk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.