Messages in this thread | | | Date | Wed, 10 Dec 2014 20:32:34 -0500 | From | Rik van Riel <> | Subject | Re: [PATCH, 3.18] sleeping function called from invalid context |
| |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/10/2014 07:51 PM, Andy Lutomirski wrote: > On Wed, Dec 10, 2014 at 4:49 PM, Rik van Riel <riel@redhat.com> > wrote: On 12/10/2014 07:46 PM, Daniel J Blueman wrote: >>>> Gah. I had some non-temporal copy changes in the wrong tree. >>>> I'll check with a definitely clean tree and follow up if it >>>> still occurs. > > The exception handlers should definitely allow sleeping, so I > suspect those changes may be related. > >> It would be really, really nice if we could arrange for >> kernel_fpu_begin to be unconditionally usable in anything except >> NMI context. The crypto code would be much less scary, we could >> make non-temporal copies safe, etc. Can we have ponies, too?
Isn't it already?
I see nothing in __kernel_fpu_begin that looks like it would ever need to sleep.
- -- All rights reversed -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEcBAEBAgAGBQJUiPQyAAoJEM553pKExN6DKJoH/iWa64YibC17ADt2F7Uq4sSD 7gsi7oG7t/WJGUH5QbWy3O+36ppTw2lZwLMUUlPMqHaqzyhNa8TkGr2auyJyH45h vk7YCBpHjzqGB8IUxgbeaie6n95Z8RG28FP8HOB1EjCwQwqJR3lQqnvRP6QD17FX H/I9+w5+Hdkcu0sNj8jppdap+q6Bu/y1WHli3iWIlHMJIsfMMmkmiZR/Gw0ewf0w F8bePmQYQjyB/xkEPtfXFGUuJfnbLYkYFyHUHHe/J+/MI1VkKNPDBGelvNKwniEC 41R7KinuqVh6DiAa9WprAXcrmllHI4L5aIFIRWI/W03/omFrF6WAdWs8OXioHfI= =s4Eb -----END PGP SIGNATURE-----
| |