|Subject:||Re: VCE exceptions|
|From:||"William J. Earl" <firstname.lastname@example.org>|
|Date:||Fri, 3 Apr 1998 14:07:50 -0800|
|Cc:||"William J. Earl" <email@example.com>, firstname.lastname@example.org, email@example.com|
|References:||<firstname.lastname@example.org> <199804022141.NAA01565@fir.engr.sgi.com> <email@example.com> <199804022315.PAA01986@fir.engr.sgi.com> <firstname.lastname@example.org> <199804031911.LAA21028@fir.engr.sgi.com> <email@example.com>|
firstname.lastname@example.org writes: ... > Anyway, we have to deal with the problem and I'm going to hope the people > that actually have machines with SC/MC CPUs were the hardware detects the > problem for us will help me by running test kernels. ... They can help by having the hardware show some of the cases where the software is doing the wrong thing, but a reliable system will require a solution which works on an R5000 or R4600, where there is no hardware detection. That is, in most cases where an R4000SC would give you a VCE, an R5000 will give you corrupted data (in general, not every time). The solution needs to be correct by construction, not by testing.
|<Prev in Thread]||Current Thread||[Next in Thread>|