From: Stanislav Meduna <stano@meduna.org>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org, gunnarlindroth@hotmail.com,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Floating point problems on UML - help needed
Date: Thu, 18 Aug 2011 08:29:16 +0200 [thread overview]
Message-ID: <4E4CB13C.7010502@meduna.org> (raw)
In-Reply-To: <4E4C2B6F.7000800@nod.at>
On 17.08.2011 22:58, Richard Weinberger wrote:
> It looks like FPU registers get sometimes lost after switching between
> two or more threads.
This is probably a bug in UML I reported nearly three years ago.
For me mode=skas0 worked aruond the issue.
http://thread.gmane.org/gmane.linux.uml.devel/11824/focus=11840
You might try the patch posted in
http://thread.gmane.org/gmane.linux.uml.devel/12158
(I don't have the environment to test it anymore)
Regards
--
Stano
next prev parent reply other threads:[~2011-08-18 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 20:58 Floating point problems on UML - help needed Richard Weinberger
2011-08-18 6:29 ` Stanislav Meduna [this message]
2011-08-18 10:45 ` [uml-devel] " Richard Weinberger
2011-08-18 11:36 ` Ingo van Lil
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=4E4CB13C.7010502@meduna.org \
--to=stano@meduna.org \
--cc=gunnarlindroth@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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