public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Quim K Holland <qkholland@my-deja.com>
Cc: dledford@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: cpu_has_fxsr or cpu_has_xmm?
Date: Fri, 23 Feb 2001 13:44:14 -0800	[thread overview]
Message-ID: <3A96D9AE.C320EC1@transmeta.com> (raw)
In-Reply-To: <200102232051.MAA18803@mail17.bigmailbox.com>

Quim K Holland wrote:
> 
> DL> As to the correctness, the mxcsr register really only exists
> DL> if you have xmm, so the xmm is the correct test. However,...
> 
> DL> ...  User space programmers should be checking for xmm
> DL> capability themselves before ever paying attention to mxcsr
> DL> anyway, so it's not an end of the world error.
> 
> If that is the case, wouldn't it be simpler to always return
> tsk->thread.i387.fxsave.mxcsr from this function, and initialize
> that field to 0x1f80 (whatever that magic number means) when
> the structure is built?
> 

No, because the CPU *may* overwrite it when you do an FXSAVE.

	-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 21:44 UTC|newest]

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

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=3A96D9AE.C320EC1@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=dledford@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qkholland@my-deja.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