mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, "Nakajima,
	Jun" <jun.nakajima@intel.com>,
	"Mallick, Asit K" <asit.k.mallick@intel.com>,
	"Saxena, Sunil" <sunil.saxena@intel.com>
Subject: Re: [PATCH] mxcsr patch for i386 & x86-64
Date: Tue, 4 May 2004 12:26:29 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0405041225080.3271@ppc970.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0405041201440.3271@ppc970.osdl.org>



On Tue, 4 May 2004, Linus Torvalds wrote:
> 
> Right now you export a function that does just a simple mask operation, 
> and quite frankly, that just seems to make it less clear what the code is 
> doing. So who not get rid of that "set_fpu_mxcsr()" function, and just 
> replace all the "0xffbf" uses with "mxcsr_feature_mask"?

I also note that the x86-64 version of has "mxcsr" as "unsigned short" in 
set_fpu_mxcsr(). I'd have expected these changes to make it possible to 
have feature bits in the high 16 bits too, no?

		Linus

  reply	other threads:[~2004-05-04 19:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04 18:50 Kamble, Nitin A
2004-05-04 19:10 ` Linus Torvalds
2004-05-04 19:26   ` Linus Torvalds [this message]
2004-05-04 20:24     ` Linus Torvalds
2004-05-04 21:07       ` Jeff Garzik
2004-05-05 13:51       ` Pavel Machek
2004-05-04 20:25 Kamble, Nitin A
2004-05-04 21:06 Kamble, Nitin A
2004-05-04 21:47 Nakajima, Jun
2004-05-06 21:00 Kamble, Nitin A
2004-05-07 14:23 ` Pavel Machek
2004-05-07  1:40 Kamble, Nitin A

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=Pine.LNX.4.58.0405041225080.3271@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=akpm@osdl.org \
    --cc=asit.k.mallick@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nitin.a.kamble@intel.com \
    --cc=sunil.saxena@intel.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®