:> :> By the way, following command could be used to check how kernel has :> been compiled, regarding the CPU_FXSAVE_LEAK option: :> :> objdump -x /boot/kernel/kernel | grep fpu_clean_state : :The patch looks fine to me, but can it be CPU_FXSAVE_NOLEAK ? :so only people know the problem will turn it on. : :David Xu I don't think it really needs to be optioned. Since the FPU state is demand-loaded from a trap/exception anyway, a huge amount of code is run in the same path that fpu_clean_state is called from. fpu_clean_state itself only eats a few nanoseconds (like maybe ~1/10 of the time that fninit takes). -MattReceived on Sun May 21 2006 - 21:51:53 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:56 UTC