In article <3A846C84.109F1D7D@colorfullife.com>,
Manfred Spraul <manfred@colorfullife.com> wrote:
>
>* use sse for normal memcopy. Then main advantage of sse over mmx is
>that only the clobbered registers must be saved, not the full fpu state.
>
>* verify that the code doesn't break SSE enabled apps.
>I checked a sse enabled mp3 encoder and Mesa.
Ehh.. Did you try this with pending FPU exceptions that have not yet
triggered?
I have this strong suspicion that your kernel will lock up in a bad way
of you have somebody do something like divide by zero without actually
touching a single FP instruction after the divide (so that the error has
happened, but has not yet been raised as an exception).
And when it hits your SSE copy routines with the pending error, it will
likely loop forever on taking the fault in kernel space.
Basically, kernel use of MMX and SSE are a lot harder to get right than
many people seem to realize. Why do you think I threw out all the
patches that tried to do this?
And no, the bug won't show up in any normal testing. You'll never know
about it until somebody malicious turns your machine into a doorstop.
Finally, did you actually see any performance gain in any benchmarks?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 09 2001 - 17:41:57 EST