Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state changes

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Herbert Xu
Date: Monday, August 11, 2008 - 5:39 pm

On Mon, Aug 11, 2008 at 01:19:01PM -0700, Suresh Siddha wrote:
.

Yes disabling preemption is the real killer.

This is just a quick band-aid.  Longer term we should add a task
flag that indicates the task is currently doing kernel FPU which
will tell the scheduler to clear TS the next time it's run.  That
way we won't need to disable preemtion or pollute the user task's
FPU used state.

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Kernel oops with 2.6.26, padlock and ipsec: probably p ..., Herbert Xu, (Mon Aug 11, 5:39 pm)