From: Blue Swirl <blauwirbel@gmail.com>
To: bifferos <bifferos@yahoo.co.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Emulation of early 486 CPUs (no fpu, no cpuid)
Date: Tue, 1 Sep 2009 19:39:09 +0300 [thread overview]
Message-ID: <f43fc5580909010939o105fa3f8j283963fb44d02af@mail.gmail.com> (raw)
In-Reply-To: <476105.70627.qm@web27005.mail.ukl.yahoo.com>
On Tue, Sep 1, 2009 at 3:05 PM, bifferos<bifferos@yahoo.co.uk> wrote:
> Hi,
>
> I'm trying to emulate a 486SX CPU, so was wondering how to knock out cpuid and fpu. I've changed the definition of ID_MASK in target-i386/cpu.h to zero, and this prevents Linux from detecting cpuid capability. Bit of a hack, because the instruction is still there, but never mind. I've been trying to work out how to disable fpu emulation so Linux falls back on software emulation.
>
> Can someone throw me a bone?
x86 CPU support is a bit primitive compared to PPC, ARM or Sparc. On
those targets there are plenty of CPU types to choose from and if that
is not enough, there are ways to modify the cpu features. The CPU type
also influences instruction translation: without an FPU, floating
point instructions trap on Sparc.
There may be an order of magnitude more x86 CPU types than all other
targets combined, so we may not want to support all of them but at
least the x86 feature selection support and translation should be more
flexible.
prev parent reply other threads:[~2009-09-01 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 12:05 [Qemu-devel] Emulation of early 486 CPUs (no fpu, no cpuid) bifferos
2009-09-01 16:39 ` Blue Swirl [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=f43fc5580909010939o105fa3f8j283963fb44d02af@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=bifferos@yahoo.co.uk \
--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).