From: "David S. Miller" <davem@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: Re: [BK-2.5] Move "used FPU status" into new non-atomic thread_info->status field.
Date: Mon, 10 Mar 2003 10:56:59 -0800 (PST) [thread overview]
Message-ID: <20030310.105659.57012503.davem@redhat.com> (raw)
In-Reply-To: <200303101905.h2AJ56P00946@hera.kernel.org>
From: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Date: Mon, 10 Mar 2003 18:20:35 +0000
Linus said, in a recent BK changelog:
Also, fix x86 FP state after fork() by making sure the FP is unlazied
_before_ we copy the state information. Otherwise, if a process did a
fork() while holding the FP state lazily in the registers, the child
would incorrectly unlazy bogus state.
At least on sparc{32,64}, we consider FPU state to be clobbered coming
into system calls, this eliminates a lot of hair wrt. FPU state
restoring in cases such as fork().
Are you preserving FPU state across fork() on x86? If so, what do you
think might rely on this?
next parent reply other threads:[~2003-03-10 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200303101905.h2AJ56P00946@hera.kernel.org>
2003-03-10 18:56 ` David S. Miller [this message]
2003-03-10 19:25 ` [BK-2.5] Move "used FPU status" into new non-atomic thread_info->status field Linus Torvalds
2003-03-10 19:14 ` David S. Miller
2003-03-10 19:59 ` Chris Friesen
2003-03-10 20:09 ` Linus Torvalds
[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
2003-03-11 0:56 Mikael Pettersson
2003-03-11 1:02 ` Linus Torvalds
2003-03-11 12:59 ` Mikael Pettersson
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=20030310.105659.57012503.davem@redhat.com \
--to=davem@redhat.com \
--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