xen-devel

[Top] [All Lists]

[Xen-devel] [PATCH] FPU stack fault handling

from [Charles Coffing]

[Permanent Link][Original]

To:	<xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] [PATCH] FPU stack fault handling
From:	"Charles Coffing" <ccoffing@xxxxxxxxxx>
Date:	Thu, 05 Aug 2004 14:55:51 -0600
Delivery-date:	Thu, 05 Aug 2004 22:07:02 +0100
Envelope-to:	steven.hand@xxxxxxxxxxxx
List-archive:	<http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help:	<mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id:	List for Xen developers <xen-devel.lists.sourceforge.net>
List-post:	<mailto:xen-devel@lists.sourceforge.net>
List-subscribe:	<https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe:	<https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender:	xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx

The sparse Linux trees have diverged from mainstream Linux in their
handling of FPU errors.  I think mainstream Linux is correct.

According to the Pentium developer's manual in section 7.1.9, a stack
fault is a type of invalid operation.  So stack faults will have the
invalid op bit set.  The attached patch restores this behavior.


(Something mangled my previous inline patch, so I'm attaching this one
instead.  Let's see if this one survives...)

--Charles

fpu.patch
Description: Binary data

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] [PATCH] FPU stack fault handling, Charles Coffing <=

Previous by Date:	[Xen-devel] EXPORT_SYMBOL, Charles Coffing
Next by Date:	Re: [Xen-devel] Xen & Automated Disk Management for Domains, Brian Wolfe
Previous by Thread:	[Xen-devel] EXPORT_SYMBOL, Charles Coffing
Next by Thread:	[Xen-devel] EXPORT SYMBOL in evtchn.c breaks 2.4.26-xen0, Sven Kretzschmar
Indexes:	[Date] [Thread] [Top] [All Lists]