Re: [RFC] framework for fpu usage in kernel

[Alan Cox]

> memcopy is a really generic function, and calling it saves the current
> fpu state into thread.i387.f{,x}save. IMHO that's wrong, memcopy must
> save into a local buffer like raid5 checksumming.

The mmx copy is only done in task context. There are a whole variety
of _horrible_ problems doing it in interrupt space so based on the 
considerable number of problems with prior attempts to get it right on
IRQ and copyuser cases I didnt bother