-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/23/2015 12:22 AM, Andy Lutomirski wrote: > On Sun, Feb 22, 2015 at 5:45 PM, Rik van Riel <r...@redhat.com> > wrote:
>> One implication of this is that in kernel mode, we can no longer >> just assume that the user space FPU state is always loaded, and >> we need to check for that (like the lazy FPU code does today). I >> would really like to keep that code around, for obvious reasons >> :) > > I like that stuff, except for the fact that it still has code that > depends on whether we're in eager or lazy mode, even though eager > is a little less eager with your patches. Ideally I'd like to see > your patches applied *and* lazy mode removed. The latest version of my code (which I should forward-port again to the latest tip bits) simplifies things a lot. It moves all new task handling to switch_fpu_finished(), which is called from do_notify_resume(). At that point we either load the FPU context, or we set CR0.TS. - -- All rights reversed -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU6yI3AAoJEM553pKExN6DyQEH/13E0T6wsII5L+0W1D0WU4v5 F2SmU74zvCv+RhRl/0npvKRQC3IkZ/peM9h/1PU/r61Y39VhexUxiUZ86afzz4KJ ogPNEs6HZ8UYSji6RPlVsuJJ4vCsZ9GA+27JwKGzLUG1NfniL0qlc93rl+f3ZfFm 5H4bjtcO361Am15yKkFPRl/0PKqRhMDa4tzJGkvvCaJ+k195Ik0a7WXjOlGdIeJA 5Q1D0qaAccXtwfNjqhxIfTBi1LV2a1/jCKF8ktxGJ2+Ywvau9blJnPfD8vUf9JL2 9/le1kyNU3h8B2lU0jIi4a2Y/CcU47heEUy5htmoo6wChQWAy/pR8JaE6++qWqI= =ee/J -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/