All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: mingo@kernel.org, torvalds@linux-foundation.org,
	andreas.herrmann3@amd.com, bp@amd64.org, robert.richter@amd.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] x86, fpu: enable eagerfpu by default for xsaveopt
Date: Fri, 07 Sep 2012 11:43:11 -0700	[thread overview]
Message-ID: <504A403F.10501@zytor.com> (raw)
In-Reply-To: <1347042703-11128-2-git-send-email-suresh.b.siddha@intel.com>

On 09/07/2012 11:31 AM, Suresh Siddha wrote:
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index 6273099..b21bcbd 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -1835,7 +1835,7 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>   			enabling legacy floating-point and sse state.
>
>   	eagerfpu=	[X86]
> -			on	enable eager fpu restore
> +			on	enable eager fpu restore (default for xsaveopt)
>   			off	disable eager fpu restore
>

Should we make this a tristate (on, off, default/auto)?

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-09-07 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 18:31 [PATCH 1/3] x86, fpu: decouple non-lazy/eager fpu restore from xsave Suresh Siddha
2012-09-07 18:31 ` [PATCH 2/3] x86, fpu: enable eagerfpu by default for xsaveopt Suresh Siddha
2012-09-07 18:43   ` H. Peter Anvin [this message]
2012-09-07 19:20     ` Suresh Siddha
2012-09-07 18:31 ` [PATCH 3/3] x86, fpu: move check_fpu() after alternative_instructions() Suresh Siddha
2012-09-07 18:47 ` [PATCH 1/3] x86, fpu: decouple non-lazy/eager fpu restore from xsave H. Peter Anvin
2012-09-07 19:12   ` Suresh Siddha

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=504A403F.10501@zytor.com \
    --to=hpa@zytor.com \
    --cc=andreas.herrmann3@amd.com \
    --cc=bp@amd64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=robert.richter@amd.com \
    --cc=suresh.b.siddha@intel.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 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.