All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [BK-2.5] Move "used FPU status" into new non-atomic thread_info->status field.
Date: Mon, 10 Mar 2003 14:59:53 -0500	[thread overview]
Message-ID: <3E6CEEB9.1050304@nortelnetworks.com> (raw)
In-Reply-To: Pine.LNX.4.44.0303101119220.2240-100000@home.transmeta.com

Linus Torvalds wrote:
> On Mon, 10 Mar 2003, David S. Miller wrote:
> 
>>   
>>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().
>>
> 
> We could _probably_ do it on x86 too. The standard C calling convention on 
> x86 says FPU register state is clobbered, if I remember correctly. 
> However, some of the state is "long-term", like rounding modes, exception 
> masking etc, and even if we didn't save the register state we would have 
> to save that part.
> 
> And once you save that part, you're better off saving the registers too, 
> since it's all loaded and saved with the same fxsave/fxrestor instruction 
> (ie we'd actually have to do _more_ work to save only part of the FP 
> state).

Does this open the door for using FP in the kernel?

Chris


-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


  parent reply	other threads:[~2003-03-10 19:49 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 ` [BK-2.5] Move "used FPU status" into new non-atomic thread_info->status field 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 [this message]
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=3E6CEEB9.1050304@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.