From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] arm64: advertise availability of CRC and crypto instructions
Date: Mon, 20 Jan 2014 17:38:38 +0000 [thread overview]
Message-ID: <20140120173838.GD29971@arm.com> (raw)
In-Reply-To: <1387807592-26375-1-git-send-email-ard.biesheuvel@linaro.org>
On Mon, Dec 23, 2013 at 02:06:27PM +0000, Ard Biesheuvel wrote:
> This series is a followup to the patch that was recently merged by Catalin that
> allocates hwcaps bits for CRC and Crypto Extensions instructions so userland can
> discover whether the current CPU has any of those capabilities.
>
> Patch #1 enables ARM support for the ELF_HWCAP2/AT_HWCAP2 ELF auxv entry that
> was recently added to the kernel and glibc (2.18). It extends the feature bit
> space to 64 bits (on 32-bit architectures)
>
> Patch #2 adds generic support for ELF_HWCAP2/AT_HWCAP2 to the 32-bit ELF compat
> mode for 64-bit architectures.
>
> Patch #3 adds support for ELF_HWCAP2/AT_HWCAP2 to arm64's 32-bit ELF compat mode
>
> Patch #4 allocates the HWCAP2 bits in the arch/arm tree. This is necessary
> because 32-bit ARM binaries can execute both under ARM and under arm64 kernels,
> so there should be agreement about the meaning of feature bits, even if the ARM
> kernel has no support yet for ARMv8 32-bit only hardware (such as ARMv8-R).
It looks a bit strange to start filling HWCAP2 before HWCAP is full but
I guess we want to preserve some future extensions in HWCAP for older
glibc.
--
Catalin
next prev parent reply other threads:[~2014-01-20 17:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 14:06 [PATCH v2 0/5] arm64: advertise availability of CRC and crypto instructions Ard Biesheuvel
2013-12-23 14:06 ` [PATCH v2 1/5] ARM: add support for AT_HWCAP2 ELF auxv entry Ard Biesheuvel
2014-01-20 17:39 ` Catalin Marinas
2013-12-23 14:06 ` [PATCH v2 2/5] binfmt_elf: add ELF_HWCAP2 to compat auxv entries Ard Biesheuvel
2014-01-20 17:40 ` Catalin Marinas
2014-02-05 14:08 ` Ard Biesheuvel
2013-12-23 14:06 ` [PATCH v2 3/5] arm64: add AT_HWCAP2 support for 32-bit compat Ard Biesheuvel
2013-12-23 14:06 ` [PATCH v2 4/5] ARM: introduce HWCAP2 feature bits for ARMv8 Crypto Extensions Ard Biesheuvel
2014-01-20 17:41 ` Catalin Marinas
2013-12-23 14:06 ` [PATCH v2 5/5] arm64: advertise ARMv8 extensions to 32-bit compat ELF binaries Ard Biesheuvel
2014-01-20 17:43 ` Catalin Marinas
2014-01-07 9:22 ` [PATCH v2 0/5] arm64: advertise availability of CRC and crypto instructions Ard Biesheuvel
2014-01-20 17:38 ` Catalin Marinas [this message]
2014-01-20 17:44 ` Nicolas Pitre
2014-01-20 18:03 ` Ard Biesheuvel
2014-01-20 18:17 ` Nicolas Pitre
2014-01-20 18:32 ` Ard Biesheuvel
2014-01-20 18:55 ` Nicolas Pitre
2014-01-20 19:01 ` Ard Biesheuvel
2014-01-20 19:42 ` Nicolas Pitre
2014-01-21 15:12 ` Catalin Marinas
2014-01-21 8:55 ` Ard Biesheuvel
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=20140120173838.GD29971@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).