linux-kernel - Re: [PATCH] crypto: aes - make assembler implementation default for i386 and x86-64

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120620144907.19996rt0vpgn7zys@www.81.fi>
Date:	Wed, 20 Jun 2012 14:49:07 +0300
From:	Jussi Kivilinna <jussi.kivilinna@...et.fi>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	linux-crypto@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] crypto: aes - make assembler implementation default
 for i386 and x86-64

Quoting Herbert Xu <herbert@...dor.apana.org.au>:

> On Tue, Jun 12, 2012 at 09:25:18PM +0300, Jussi Kivilinna wrote:
>>
>> Well, how about letting arch specific assembler implementations
>> replace aes-generic
>> completely.. in this case add "depends on !X86" on
>> CRYPTO_AES_GENERIC. Hardware
>> modules get autoloaded (cpuid/pci/platform/etc) but generic
>> assembler implementation
>> might as well be replacement as it cannot autoload depending on
>> hardware support (or
>> it can, but will be always loaded).
>
> Perhaps we can just force a modprobe of a given algorithm at least
> once for each boot (when requested for the first time).  I think
> that should be easy to implement and should solve your problem
> scenario.
>
> What do you think?

Well, that could work.

-Jussi


>
> Thanks,
> --
> Email: Herbert Xu <herbert@...dor.apana.org.au>
> 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/