This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 1392] Problems with denormalized floating point numbers

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1392] Problems with denormalized floating point numbers on XEN-virtualized Linux/IA64
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 11 Dec 2008 19:38:23 -0800
Delivery-date: Thu, 11 Dec 2008 19:38:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1392-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

yamahata@xxxxxxxxxxxxx changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

------- Comment #10 from yamahata@xxxxxxxxxxxxx  2008-12-11 19:38 -------
Should be fixed by the series of change sets
18870:dd7ac569579a - 18877:e97216802360

The root cause is that fpswa fault isn't handle properly when
a bundle in question which is in a guest virtual address space
can't be gotten by xen VMM.
With the patches when VMM failed to get a bundle in a guest,
inject fpswa fault/trap. then a guest kernel gets the bundle and calls fpswa
library itself.

During the process of creating those patches, anothor issue was found.
When fpswa called by VMM returns status > 0,  fpswa fault/trap is injected
into a guest kernel and the kernel calls fpswa itself. So fpswa is called
twice. once by xen VMM, once by aguest kernel. so the result would be wrong.
Leave this issue as is assuming that no applications don't rely on
SIGFP to recover its computation with a xen vmm warning message.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list