public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>, Michael Matz <matz@suse.de>,
	Michal Hocko <mhocko@suse.cz>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] x86: Disable traditional FPU instructions too
Date: Mon, 27 Jan 2014 09:01:38 -0800	[thread overview]
Message-ID: <87ha8pqryl.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1401271742300.14101@pobox.suse.cz> (Jiri Kosina's message of "Mon, 27 Jan 2014 17:43:51 +0100 (CET)")

Jiri Kosina <jkosina@suse.cz> writes:

> On Mon, 27 Jan 2014, H. Peter Anvin wrote:
>
>> I don't think it'd hurt... although I think the above pretty much
>> requires that the code contain actual floating-point types to ever be
>> generated.  
>
> Unfortunately using float-typed constants (such as 1EexpL) are enough for 
> this to happen.

checkpatch would seem to be the right place to check for this?

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

  reply	other threads:[~2014-01-27 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 16:37 [RFC] x86: Disable traditional FPU instructions too Borislav Petkov
2014-01-27 16:41 ` H. Peter Anvin
2014-01-27 16:43   ` Jiri Kosina
2014-01-27 17:01     ` Andi Kleen [this message]
2014-01-27 17:16       ` H. Peter Anvin
2014-01-27 17:24         ` Borislav Petkov
2014-01-27 16:45   ` Borislav Petkov
2014-01-28  9:37     ` Michal Hocko
2014-01-28 10:25       ` H. Peter Anvin
2014-01-28 10:33         ` Michal Hocko

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=87ha8pqryl.fsf@tassilo.jf.intel.com \
    --to=andi@firstfloor.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matz@suse.de \
    --cc=mhocko@suse.cz \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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