From: Greg KH <gregkh@linuxfoundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-stable <stable@vger.kernel.org>,
hpa@linux.intel.com, hjl.tools@gmail.com, mingo@kernel.org,
tglx@linutronix.de, "tip-bot for H.J. Lu" <tipbot@zytor.com>,
linux-tip-commits@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [tip:x86/urgent] x86, fpu: correct the asm constraints for fxsave , unbreak mxcsr.daz
Date: Fri, 26 Jul 2013 13:25:12 -0700 [thread overview]
Message-ID: <20130726202512.GA4585@kroah.com> (raw)
In-Reply-To: <51F2D9D2.8050405@zytor.com>
On Fri, Jul 26, 2013 at 01:19:30PM -0700, H. Peter Anvin wrote:
> Hi everyone,
>
> I have tagged this one for -stable, but it is a definite "maybe", so I
> wanted to:
>
> a) qualify that tagging, and
> b) perhaps use it as a boundary case for policy clarification.
>
> This patch is an old bug, an incorrect assembly constraint, but as
> happens with this type of bug it is being exposed by a change in gcc.
> Therefore, although this is neither a regression per se in the kernel
> nor in gcc, it is a regression in the combined output.
>
> The bug is obvious; the fix at the very least *should* be obvious; the
> main source of risk would appear that it might trigger bugs in very old
> versions of gcc.
>
> The gain is less inherently obvious: currently the only MXCSR bit
> affected is DAZ, although this also affects any future MXCSR bits. Most
> users do not care about DAZ, but the ones that do generally care *a lot*
> about it as their applications may suffer very bad performance otherwise.
>
> There is a kernel bugzilla for this:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=60633
>
> ... but it doesn't really add any additional information.
Thanks for the additional information, it's much appreciated.
greg k-h
next prev parent reply other threads:[~2013-07-26 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-eaa5a990191d204ba0f9d35dbe5505ec2cdd1460@git.kernel.org>
2013-07-26 20:19 ` [tip:x86/urgent] x86, fpu: correct the asm constraints for fxsave , unbreak mxcsr.daz H. Peter Anvin
2013-07-26 20:25 ` Greg KH [this message]
2013-07-26 21:36 ` Linus Torvalds
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=20130726202512.GA4585@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tipbot@zytor.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox