qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Platte <lists@naasa.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] fpu problems with qemu-system-sparc
Date: Thu, 18 May 2006 18:16:11 +0200	[thread overview]
Message-ID: <200605181816.12353.lists@naasa.net> (raw)

Hi!

I've some problems with qemu-system-sparc and programs using floating point 
instructions. Each time at least two floating point programs are started in 
qemu simultaneously, one or both are killed by the linux kernel with a SIGSEV 
signal (sometimes because of a corrupted stack or invalid register values). 
If I start only one program no error occurs. It looks like it has something 
to do with the disabled-floating-point-unit-trap, which is executed each time 
a process tries to access the fpu while another process has used it before. 
This interrupt calls the linux function do_fpd_trap which then saves the old 
FPU-state and restores the new one. When only one program uses the FPU this 
trap is never executed.

I've checked a lot of the executed instructions in qemu and cannot find any 
problems up to now. Does somebody else has an idea what to check? The test 
program simply adds two float variables (fadds-instruction) in a loop and 
this crashes the program reproducible.

regards,
Jörg

             reply	other threads:[~2006-05-18 16:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 16:16 Joerg Platte [this message]
2006-05-18 17:53 ` [Qemu-devel] fpu problems with qemu-system-sparc Blue Swirl
2006-05-18 19:50   ` Joerg Platte
2006-05-19 18:14   ` Joerg Platte
2006-05-19 19:14     ` Blue Swirl
2006-05-19 19:38       ` Joerg Platte
2006-05-22 17:51       ` Joerg Platte
2006-05-22 19:12         ` Joerg Platte
2006-05-22 19:31           ` Joerg Platte
2006-05-23  6:26 ` Joerg Platte

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=200605181816.12353.lists@naasa.net \
    --to=lists@naasa.net \
    --cc=jplatte@naasa.net \
    --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).