Messages in this thread | | | Date | Mon, 10 Mar 2003 12:45:02 -0800 (PST) | Subject | Re: [BK-2.5] Move "used FPU status" into new non-atomic thread_info->status field. | From | "David S. Miller" <> |
| |
From: Andi Kleen <ak@suse.de> Date: 10 Mar 2003 22:01:17 +0100
Turned out the 32bit ptrace unlazy FPU path shared two lines too many with with the 32bit signal FPU saving path and was resetting the used_fpu flag. Result was that the FPU state of the child could be reinitialized in some circumstances on ptrace accesses.
So what it depended upon was the FP control register state, not the state of the individual FPU registers, across fork() right? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |