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

[H. Peter Anvin]

Wolfgang Walter wrote:
> These FPU changes are already in 2.6.26. Undoing them, would that be accepted 
> for 2.6.26 stable?
>
> Maybe the following solution would be possible: if a processor with padlock is 
> detected the memory for xstate is always allocated when the thread is created 
> instead "lazy"?

That will effectively happen, so it doesn't really matter.

The true optimization would be to recognize that the state doesn't have 
to be saved, and track when we did so, and so on and so forth.

VIA really did their customers a disservice tying this to CR0.TS.

	-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/