Followup to previous post: Atlon/VIA Instabilities
Hi,
So it seems that CONFIG_X86_USE_3DNOW is simply used to
enable access to the routines in mmx.c (the athlon-optimized routines on CONFIG_K7 kernels), so then it appears that somehow this is corrupting memory / not behaving as it should (very technical, right?) :)...
--Seth
Quoted 5 lines
So it seems that
CONFIG_X86_USE_3DNOWis simply used to
enable access to the routines inmmx.c(the athlon-optimized routines onCONFIG_K7kernels), so then it appears that somehow this is corrupting memory / not behaving as it should (very technical, right?) :)...
Feel free to go over those routines in detail by hand. I've been over them and I can't see any problems. The obvious candidates would be races in the kernel_fpu_begin/end code but that also seems watertight to me.
Quoted 10 lines · Seth Goldberg
Hi,
So it seems that
CONFIG_X86_USE_3DNOWis simply used to
enable access to the routines inmmx.c(the athlon-optimized routines onCONFIG_K7kernels), so then it appears that somehow this is corrupting memory / not behaving as it should (very technical, right?) :)...--Seth
This is a shot in the dark. Do you have floating-point emulation on (CONFIG_MATH_EMULATION=y)?
Tom
Signature · 1 line
The Daemons lurk and are dumb. -- Emerson
Hi Tom,
Nope. No emulation here. Thanks for trying tho ;).
--Seth
Quoted 20 lines · Tom Leete
Quoted 10 lines · Seth Goldberg
Hi,
So it seems that
CONFIG_X86_USE_3DNOWis simply used to
enable access to the routines inmmx.c(the athlon-optimized routines onCONFIG_K7kernels), so then it appears that somehow this is corrupting memory / not behaving as it should (very technical, right?) :)...--Seth
This is a shot in the dark. Do you have floating-point emulation on (
CONFIG_MATH_EMULATION=y)?Tom
--
The Daemons lurk and are dumb. -- Emerson