Am Mittwoch, 28. Dezember 2016, 16:59:38 CET schrieb Herbert Xu: Hi Herbert, > > 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? When I configure AES-NI as module, it works. When compiling it statically, the allocation returns an -ENOENT. Now, when I diff both config files after a simple toggle from AES-NI=y to =m I see (linux-4.10.config contains the static config, .config contains the module configuration): $ diff -urN ../linux-4.10.config .config --- ../linux-4.10.config 2016-12-28 10:56:51.805526584 +0100 +++ .config 2016-12-28 11:00:17.959608195 +0100 @@ -4062,8 +4062,8 @@ CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m CONFIG_CRYPTO_ABLK_HELPER=m -CONFIG_CRYPTO_SIMD=y -CONFIG_CRYPTO_GLUE_HELPER_X86=y +CONFIG_CRYPTO_SIMD=m +CONFIG_CRYPTO_GLUE_HELPER_X86=m # # Authenticated Encryption with Associated Data @@ -4132,7 +4132,7 @@ # CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_AES_X86_64=y -CONFIG_CRYPTO_AES_NI_INTEL=y +CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m Ciao Stephan -- 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
