WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [Xen-ia64-devel] [PATCH 1/2] [RESEND] FPSWA emulation support

To: "Masaki Kanno" <kanno.masaki@xxxxxxxxxxxxxx>, "Williamson, Alex (Linux Kernel Dev)" <alex.williamson@xxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH 1/2] [RESEND] FPSWA emulation support
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Wed, 24 May 2006 09:12:12 -0700
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 24 May 2006 09:13:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <8AC67F1BF7AD4Ekanno.masaki@xxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZ/HGNEo4TUv/gATNax+kuQWXntggALtDdA
Thread-topic: [Xen-ia64-devel] [PATCH 1/2] [RESEND] FPSWA emulation support
> >   Why do we need handle_fpu_swa_for_xen()?  Xen should 
> never hit an FP
> >error that requires this support.  Thanks,
> 
> Same as you, I think that Xen should never hit an FP error 
> that requires 
> this support. However, the time when FPSWA is necessary for 
> Xen may come.
> Therefore I'd like to leave handle_fpu_swa_for_xen().

I have to disagree.  An FP error that requires handling
by the FPSWA is very rare, even in applications that do
lots of floating point processing.

Linux/ia64 does no floating point processing, Xen/x86 does
no floating point processing, and Xen/ia64 shouldn't either.
If some developer adds floating point code into Xen/x86,
guests will break.  (This happened once last year --
someone added floating point code to compute some statistics.)

Linux/ia64 uses floating point registers only for integer
multiply/divide (and? fast copy?).  The same is true of Xen/ia64.
If any Xen/ia64 developer adds any floating point code
in Xen that could possibly cause an FPSWA, I'd rather see
a panic so that code could be removed or fixed.

Last, it is not Linux or Xen style to add code that might
possibly be used sometime in the future.  A kernel and a
hypervisor should be as small as possible and adding
even a few hundred bytes of code that maybe will be
executed sometime in the future (or, in my opinion, never
should be) is bad style.  At best, the code should be
surrounded by an "#if 0", and I don't think even that
is a good idea.

Just my opinion... others may disagree.
Dan

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel