From: Herbert Xu <herbert@gondor.apana.org.au>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux@arm.linux.org.uk,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, davem@davemloft.net,
arnd@arndb.de
Subject: Re: [PATCH] crypto: arm: workaround for building with old binutils
Date: Mon, 13 Apr 2015 12:12:37 +0800 [thread overview]
Message-ID: <20150413041236.GA11091@gondor.apana.org.au> (raw)
In-Reply-To: <1428759154-16251-1-git-send-email-ard.biesheuvel@linaro.org>
On Sat, Apr 11, 2015 at 03:32:34PM +0200, Ard Biesheuvel wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> How about something like this:
>
> A warning will be emitted by make when descending into the arch/arm/crypto
> directory, but only if any ARMv8 Crypto modules were in fact selected.
>
> /home/ard/linux-2.6/arch/arm/crypto/Makefile:22: These ARMv8 Crypto Extensions modules need binutils 2.23 or higher
> /home/ard/linux-2.6/arch/arm/crypto/Makefile:23: aes-arm-ce.o sha1-arm-ce.o sha2-arm-ce.o ghash-arm-ce.o
>
>
> ----------------->8------------------
> Old versions of binutils (before 2.23) do not yet understand the
> crypto-neon-fp-armv8 fpu instructions, and an attempt to build these
> files results in a build failure:
>
> arch/arm/crypto/aes-ce-core.S:133: Error: selected processor does not support ARM mode `vld1.8 {q10-q11},[ip]!'
> arch/arm/crypto/aes-ce-core.S:133: Error: bad instruction `aese.8 q0,q8'
> arch/arm/crypto/aes-ce-core.S:133: Error: bad instruction `aesmc.8 q0,q0'
> arch/arm/crypto/aes-ce-core.S:133: Error: bad instruction `aese.8 q0,q9'
> arch/arm/crypto/aes-ce-core.S:133: Error: bad instruction `aesmc.8 q0,q0'
>
> Since the affected versions are still in widespread use, and this breaks
> 'allmodconfig' builds, we should try to at least get a successful kernel
> build. Unfortunately, I could not come up with a way to make the Kconfig
> symbol depend on the binutils version, which would be the nicest solution.
>
> Instead, this patch uses the 'as-instr' Kbuild macro to find out whether
> the support is present in the assembler, and otherwise emits a non-fatal
> warning indicating which selected modules could not be built.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Link: http://storage.kernelci.org/next/next-20150410/arm-allmodconfig/build.log
> Fixes: 864cbeed4ab22d ("crypto: arm - add support for SHA1 using ARMv8 Crypto Instructions")
> [ard.biesheuvel:
> - omit modules entirely instead of building empty ones if binutils is too old
> - update commit log accordingly]
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Patch applied.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2015-04-13 4:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 13:32 [PATCH] crypto: arm: workaround for building with old binutils Ard Biesheuvel
2015-04-11 20:54 ` Arnd Bergmann
2015-04-12 9:23 ` Ard Biesheuvel
2015-04-13 4:12 ` Herbert Xu [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-10 19:57 Arnd Bergmann
2015-04-11 7:41 ` Ard Biesheuvel
2015-04-11 8:55 ` Arnd Bergmann
2015-04-11 10:35 ` Ard Biesheuvel
2015-04-11 20:44 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150413041236.GA11091@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox