All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: cpu_has_fxsr or cpu_has_xmm?
Date: 22 Feb 2001 22:11:52 -0800	[thread overview]
Message-ID: <974uv8$303$1@cesium.transmeta.com> (raw)
In-Reply-To: <200102230538.VAA17793@mail23.bigmailbox.com>

Followup to:  <200102230538.VAA17793@mail23.bigmailbox.com>
By author:    "Quim K Holland" <qkholland@my-deja.com>
In newsgroup: linux.dev.kernel
>
> I've been looking at various -ac patches for the last couple of 
> weeks and have been wondering why only this piece of difference
> still remains between Linus' 2.4.2 and Alan's -ac2.  All the other
> diffs in i387.c from 2.4.1-ac2 seem to have been merged into Linus
> tree at around 2.4.2-pre1.  Could anybody explain it for me please?
> 
> --- linux.vanilla/arch/i386/kernel/i387.c       Thu Feb 22 09:05:35 2001
> +++ linux.ac/arch/i386/kernel/i387.c    Sun Feb  4 10:58:36 2001
> @@ -179,7 +179,7 @@
>  
>  unsigned short get_fpu_mxcsr( struct task_struct *tsk )
>  {
> -       if ( cpu_has_fxsr ) {
> +       if ( cpu_has_xmm ) {
>                 return tsk->thread.i387.fxsave.mxcsr;
>         } else {
>                 return 0x1f80;
> 

IMO, XMM is correct here; FXSR is incorrect.  Linus?

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

  reply	other threads:[~2001-02-23  6:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-23  5:38 cpu_has_fxsr or cpu_has_xmm? Quim K Holland
2001-02-23  6:11 ` H. Peter Anvin [this message]
2001-02-23 11:23   ` Doug Ledford
  -- strict thread matches above, loose matches on Subject: below --
2001-02-23 20:51 Quim K Holland
2001-02-23 21:44 ` H. Peter Anvin

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='974uv8$303$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.