Messages in this thread | | | Date | Mon, 23 Feb 2015 10:51:26 -0500 | From | Rik van Riel <> | Subject | Re: [RFC PATCH] x86, fpu: Use eagerfpu by default on all CPUs |
| |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/23/2015 10:03 AM, Borislav Petkov wrote: > On Mon, Feb 23, 2015 at 07:51:04AM -0500, Rik van Riel wrote: >> At that point we either load the FPU context, or we set CR0.TS. > > Right, but provided eager doesn't bring any slowdown, we can drop > the TS fiddling altogether and only load FPU context.
Agreed.
However, we would still need the rest of the kernel code to check whether userspace FPU context is loaded in the registers or not. We cannot simplify to the point of assuming that the FPU state will always be loaded when in eager mode.
- -- All rights reversed -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEcBAEBAgAGBQJU60x+AAoJEM553pKExN6DIMkIAJpZHQuojQMTUyy11EB7dx2N ZMm5PiQGW47f/BIbIwR3hwZbC385ZLdx1Nkrys8cXd3WNJInrMxf2PDaU9YtDFw1 NdybRbbsxAAaB3oJldLFUH5ouo9ePKV4RyXFgsgNH75uv6u4pesaWwUZNuLmxzrk h8/wns7Lpddr4C0ahPimEM1pXdfiFyo/0jaAiOj8o/IklXiJW25LBYUzE4ogD/2T 097wV5C8ojvS4doVD+GthxFuJFslZWxyNaRBRNqpE2LyhmjEdz2WwNTSrDtLsBK0 gKHjgD0eox/HpNkBzwaF6MOo1of2/WFNSJyRKwlwaWnRNpZ3jDfyU0VPg3yhF30= =aIKn -----END PGP SIGNATURE-----
| |