On Wed, Dec 28, 2016 at 09:37:04AM +0100, Stephan Müller wrote: > Am Donnerstag, 8. Dezember 2016, 19:40:38 CET schrieb Stephan Müller: > > Hi Herbert, > > > Am Donnerstag, 8. Dezember 2016, 19:32:03 CET schrieb Stephan Müller: > > > > Hi Herbert, > > > > > Hi Herbert, > > > > > > with the addition of the simd cipher change I seem to be unable to use the > > > AESNI ciphers. My .config contains CONFIG_CRYPTO_SIMD=y and > > > CONFIG_CRYPTO_AES_NI_INTEL=y. Those options always worked to load the > > > AES-NI > > (with "always worked" I meant the CONFIG_CRYPTO_AES_NI_INTEL=y option of > > course, that always ensured AES-NI to be present and usable) > > With 4.10-rc1, I also do not get the AES-NI implementations to work. do you > have any ideas what may be the issue? I'm having problems reproducing this. Does it work for you if you build them as modules? Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
