[lkml]   [2001]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] framework for fpu usage in kernel
Alan Cox wrote:
> > 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
Even task context is dangerous:

What if a drm module wants to use the fpu and then uses memcpy() after
modifying the ftp registers?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:13    [W:1.563 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site