mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@user.it.uu.se>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK-2.5] Move "used FPU status" into new non-atomic thread_info->status field.
Date: Tue, 11 Mar 2003 13:59:21 +0100	[thread overview]
Message-ID: <15981.56745.912228.109975@gargle.gargle.HOWL> (raw)
In-Reply-To: <Pine.LNX.4.44.0303101658210.6802-100000@home.transmeta.com>

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

  reply	other threads:[~2003-03-11 12:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11  0:56 Mikael Pettersson
2003-03-11  1:02 ` Linus Torvalds
2003-03-11 12:59   ` Mikael Pettersson [this message]
     [not found] <20030310.105659.57012503.davem@redhat.com.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.44.0303101119220.2240-100000@home.transmeta.com.suse.lists.linux.kernel>
2003-03-10 21:01   ` Andi Kleen
2003-03-10 20:45     ` David S. Miller
2003-03-10 21:28       ` Andi Kleen
     [not found] <200303101905.h2AJ56P00946@hera.kernel.org>
2003-03-10 18:56 ` David S. Miller
2003-03-10 19:25   ` Linus Torvalds
2003-03-10 19:14     ` David S. Miller
2003-03-10 19:59     ` Chris Friesen
2003-03-10 20:09       ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15981.56745.912228.109975@gargle.gargle.HOWL \
    --to=mikpe@user.it.uu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®