On Thu, Oct 07, 2021 at 09:03:32PM +0200, Sebastian Andrzej Siewior wrote: > > Now that you bring it up, I was under the impression that the > "SIMD-disabled" flag is only changed by the tcrypt module not by the > individual tests which are performed at the algorithm lookup time. If it > is the latter than yes, it will be painful. If it is just tcrypt then > you could wrap the whole test-suite (at module init's time) into the > kworker and bind it to one CPU). > > Maybe Peter can bring light into the temporary workaround but it does > look like simplest thing here. Let's use migrate_disable for now. If something better comes along we can always change again. Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
