arm64: advertise availability of CRC and crypto instructions
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] arm64: advertise availability of CRC and crypto instructions
Quoted 12 lines · Ard Biesheuvel
Quoted 9 lines · Russell King - ARM Linux
If we allocate the ARM64 private never-will-appear-on-ARM hwcaps in bit 32 and above, they'll be hidden from 32-bit stuff. Hopefully, glibc doesn't concatenate the HWCAP and HWCAP2 fields though - someone should check that.
Since the bits in the ARM64 hwcap are different from the ARM32 hwcap, I don't see any point in defining them for ARM32 - userspace needs to make the definition conditional anyway, and can't interpret the bits as-is because ARM64 already omits many of the ARM32 ones.
Quoted 5 lines
Please note that this is about the compat bits, not the ARM64 specific ones. These correspond 1:1 with the ARM32 ones. The idea is that a binary built for ARM will have access to the extended instructions which ARM64 offers to ARM32 binaries running in 32 bit compatibility mode (such as AES, SHAx etc).
This all sounds rather silly IMHO. As ARM32 natively doesn't support these instructions, why should running an ARM32 binary under ARM64 end up offering this?
If the ARM64 additional instructions are to be used, surely it's not unreasonable to require ARM64 native applications?
In order to use these new instructions, you're going to have to build using 64-bit anyway, at which point you have the problem of linking 32-bit applications with 64-bit libraries, and the inherent incompatibility in the API between the two. Remember, in 64-bit mode, your pointers are 64-bit whereas in 32-bit mode, they're 32-bit.
Frankly, I don't see the point, not do I see what you're talking about being technically possible.