The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Brian Gerst <bgerst@didntduck.org>
Cc: akpm@osdl.org, chrisw@osdl.org, linux-kernel@vger.kernel.org,
	virtualization@lists.osdl.org
Subject: Re: [PATCH 0/6] i386 virtualization patches, Set 3
Date: Mon, 15 Aug 2005 20:33:34 -0700	[thread overview]
Message-ID: <43015E8E.5020105@vmware.com> (raw)
In-Reply-To: <43015894.1090307@didntduck.org>

Brian Gerst wrote:

> If you really want to test the math emu code, you can hack check_x87 
> in head.S to always leave the fpu disabled.  Then you can test it on 
> any cpu, not just a 386. 


That is a good idea, and while a valid point, it actually still requires 
writing the code to actually test the FPU, specifically, using weird 
prefixes, LDT based segments, and other oddities that don't get 
generated from "normal" C code.  I'm pretty sure the existing code works 
for the 99% cases or else it wouldn't have gotten there in the first 
place.  But testing the corner cases here is even nastier than testing 
the LDT corner cases - you would basically need to write a lot of hand 
coded i387 assembler.  Perhaps such a test might exist, but in all 
honesty, without a comprehensive test, it is simply far too easy to 
introduce a bug here, and far too likely it will either not be noticed 
until it has caused someone a possibly undetected numerical error, or 
I'm just wasting my time because noone is using this code anyways.  
Fortunately, the Hubble telescope has been upgraded to a 486 ;)

Zach

  reply	other threads:[~2005-08-16  3:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 22:58 [PATCH 0/6] i386 virtualization patches, Set 3 zach
2005-08-15 23:24 ` Andi Kleen
2005-08-15 23:27   ` David Lang
2005-08-15 23:35     ` Andi Kleen
2005-08-16  3:08 ` Brian Gerst
2005-08-16  3:33   ` Zachary Amsden [this message]
2005-08-16  7:44 ` Chris Wright

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=43015E8E.5020105@vmware.com \
    --to=zach@vmware.com \
    --cc=akpm@osdl.org \
    --cc=bgerst@didntduck.org \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.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