Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 11 Mar 2003 07:48:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 11 Mar 2003 07:48:45 -0500 Received: from meryl.it.uu.se ([130.238.12.42]:20217 "EHLO meryl.it.uu.se") by vger.kernel.org with ESMTP id ; Tue, 11 Mar 2003 07:48:44 -0500 From: Mikael Pettersson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15981.56745.912228.109975@gargle.gargle.HOWL> Date: Tue, 11 Mar 2003 13:59:21 +0100 To: Linus Torvalds Cc: linux-kernel@vger.kernel.org Subject: Re: [BK-2.5] Move "used FPU status" into new non-atomic thread_info->status field. In-Reply-To: References: <200303110056.h2B0uo6U005286@harpo.it.uu.se> X-Mailer: VM 6.90 under Emacs 20.7.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 768 Lines: 17 Linus Torvalds writes: > > Sorry for being dense, but can you clarify: will current 2.{2,4,5} > > kernels preserve or destroy the parent process' FPU control at fork()? > > They're guaranteed to preserve the control state (it has to: you can't > just change the exception mask over a function call). However, that was > buggy at least in 2.5.x, and very possibly in 2.4.x too - haven't checked. Thanks. Our use of unmasked FPU exceptions should be safe then, unless 2.4 also has the bug you fixed in 2.5. /Mikael - 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/