linux-kernel - Re: [PATCH v2 1/5] x86, fpu: decouple non-lazy/eager fpu restore from xsave

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 17 Sep 2012 21:11:08 +0200
From:	Pavel Machek <pavel@....cz>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
Cc:	hpa@...or.com, mingo@...nel.org, torvalds@...ux-foundation.org,
	andreas.herrmann3@....com, bp@...64.org, robert.richter@....com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/5] x86, fpu: decouple non-lazy/eager fpu restore
 from xsave

Hi!

irely omitted.
>  			and restore using xsave. The kernel will fallback to
>  			enabling legacy floating-point and sse state.
>  
> +	eagerfpu=	[X86]
> +			on	enable eager fpu restore
> +			off	disable eager fpu restore
> +

Hmm. Only useful piece of information here is that this is about FPU
_restore_. Otherwise it tells the user exactly nothing.

Why would user want to enable it? Disable it? What is the default?

    	       	       	      	  	      	      	  Pavel 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/