Messages in this thread | | | From | Wolfgang Walter <> | Subject | Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state changes | Date | Sat, 9 Aug 2008 19:02:23 +0200 |
| |
Am Samstag, 9. August 2008 18:10 schrieb H. Peter Anvin: > Wolfgang Walter wrote: > > How could any kernel code use MMX/SSE/FPU when the interrupt case isn't > > handled? > > I don't think we have ever allowed MMX/SSE/FPU code in interrupt > handlers. kernel_fpu_begin()..end() lock out preemption, and so could > only be interrupted, not preempted.
What about
arch/x86/lib/mmx_32.c
and then
include/asm-x86/string_32.h
couldn't memcpy end as beeing implemented with MMX? And interrupt handlers may use memcpy? Or did I miss something?
Similar: couldn't memcpy be called in asynchronous way, say a page fault or someting like that?
Regards, -- Wolfgang Walter Studentenwerk München Anstalt des öffentlichen Rechts Leiter EDV Leopoldstraße 15 80802 München Tel: +49 89 38196 276 Fax: +49 89 38196 150 Email: wolfgang.walter@stwm.de http://www.studentenwerk-muenchen.de/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |