public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Thorsten Otto <admin@tho-otto.de>
To: Brad Boyer <flar@allandria.com>
Cc: linux-m68k@vger.kernel.org
Subject: Re: Software FPU emulation in linux kernel
Date: Tue, 04 Mar 2025 06:24:30 +0100	[thread overview]
Message-ID: <49758471.MN2xkq1pzW@earendil> (raw)
In-Reply-To: <20250303221012.GA7422@allandria.com>

On Montag, 3. März 2025 23:10:12 CET Brad Boyer wrote:
> On the variants without the built-in FPU, it's
> expected that the FPU emulator handles all of it since that's faster
> than triggering the emulator for each FPU instruction used in FPSP.

Yes, that's why i was wondering that a lot of functions are not implemented.

> Well, most programs that use FPU instructions aren't going to use anything
> beyond the basics.

Thats true. But if they do, wouldn't it be better to just abort the program so 
the user will notice it, rather than continuing with totally bogus values? 
Currently, uprint will just use the kernels printk. I guess that will just end 
up in the syslog for most cases, and not even seen by the user.

> The 68881/68882 are kind of unusual in implementing
> all of that in hardware.

Its not really unusual. The x87 FPU has almost the same instructions.

> In practice, no. There's a lot of other issues as well. I seem to
> recall that it only supports the 020/030 and not the versions of
> the 040/060 without FPU.

Thats mostly a matter how it is integrated in the system. That will obviously 
be totally different in my case.

> The advice
> has always been to use a full 68040/68060 or add a real 68881/68882
> chip to the 020/030 systems.

Sure. But obviously this is not always possible, otherwise we would not need 
an emulator. Nowadays, 68EC040 are much easier to find than full 68040.

> Most existing 68LC040 chips also have the bug that causes missed
> page faults after software-emulated instructions as well

Oh, i didn't know that. But handling pagefaults is another thing. But freemint 
does not manage virtual memory, so that should not be a problem here.






  reply	other threads:[~2025-03-04  5:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 16:22 Software FPU emulation in linux kernel Thorsten Otto
2025-03-03 22:10 ` Brad Boyer
2025-03-04  5:24   ` Thorsten Otto [this message]
2025-03-04  5:48     ` Brad Boyer
2025-03-03 23:38 ` Michael Schmitz
2025-03-04  4:44   ` Finn Thain
2025-03-04  5:47   ` Thorsten Otto
2025-03-06 15:24 ` Thorsten Otto

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=49758471.MN2xkq1pzW@earendil \
    --to=admin@tho-otto.de \
    --cc=flar@allandria.com \
    --cc=linux-m68k@vger.kernel.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