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

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Wolfgang Walter <wolfgang.walter@...>
Cc: Suresh Siddha <suresh.b.siddha@...>, H. Peter Anvin <hpa@...>, netdev@vger.kernel.org <netdev@...>, linux-kernel@vger.kernel.org <linux-kernel@...>, Ingo Molnar <mingo@...>, viro@ZenIV.linux.org.uk <viro@...>, vegard.nossum@gmail.com <vegard.nossum@...>
Date: Tuesday, August 12, 2008 - 8:02 am

On Tue, Aug 12, 2008 at 01:43:22PM +0200, Wolfgang Walter wrote:

Thanks a lot for testing this Wolfgang!


That's not surprising since tcrypt runs with BH off so it'll
do pretty much the same thing as before.  This also shows that
reading CR0 doesn't impose any extra overhead compared to what
was done in kernel_fpu_begin.

Cheers,
-- 
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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
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 pro..., Herbert Xu, (Tue Aug 12, 8:02 am)