qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Switch to OpenBIOS for Sparc32/64?
Date: Wed, 14 Jun 2006 14:22:53 +0200	[thread overview]
Message-ID: <448FFF9D.8080807@bellard.org> (raw)
In-Reply-To: <BAY104-F39D02E1E519B79828479E4FF8B0@phx.gbl>

Blue Swirl wrote:

> I included other fixes currently needed for correct operation (clock 
> year fix, FPU fix by Joerg Platte, MMU no-fault fix).

Note: the FPU "fix" should be revisited because it is really not 
optimal. Here are some ideas to implement it better:

1) Include the bit 'psref' in the static translation state (in 
tb->flags). Then psref can be tested at translation time and there is no 
run time cost. This approach is used on the x86 target. The downside is 
that two TBs may be generated for a given block of code depending on the 
psref value. Ideally if no FPU operations are used in the TB, psref 
should be ignored (not done yet on x86).

2) Keep psref dynamic, but test it only once per TB using FPU 
operations. In case of exception, rebuilt the CPU state as with MMU 
exceptions so that save_state() is not needed.

I tend to prefer the solution (1).

Fabrice.

  parent reply	other threads:[~2006-06-14 12:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 15:40 [Qemu-devel] Switch to OpenBIOS for Sparc32/64? Blue Swirl
2006-06-08 21:45 ` Fabrice Bellard
2006-06-14 12:22 ` Fabrice Bellard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-18  9:29 Blue Swirl
2006-06-09  2:09 Armistead, Jason
2006-06-07 15:56 Blue Swirl
2006-06-07 16:17 ` Paul Brook
2006-06-07 16:38   ` Natalia Portillo
2006-06-07 16:54     ` Joshua Root
2006-06-07 17:01       ` Natalia Portillo
2006-06-07 19:24   ` Blue Swirl
2006-06-07 19:48     ` Paul Brook

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=448FFF9D.8080807@bellard.org \
    --to=fabrice@bellard.org \
    --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).