[roll] Roll fuchsia [starnix] AT_HWCAP{,2} from zircon reported features
As found in b/452758916, boringssl in starnix userland does not know
about the hardware's crypto capability and falls back to chacha20
for all TLS connections, which is a pure software implementation.
While I am here, also expose the same information in `/proc/cpuinfo`
so that applications not using `getauxval` can also learn about the
right capabilities.
Verified with `bssl speed -filter AES-128-GCM`, see numbers posted in
http://b/452758916#comment5.
Verified with `cat /proc/cpuinfo` and compared with linux running on
the same hardware. HWCAP_EVTSTRM is the diff right now, but I am
unaware of any applications looking for this.
Tested with OOBE.
Original-Bug: 452758916
Original-Fixed: 459777055, 392598058
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1421674
Original-Revision: f1cb1c3e9d61c2628f705007ddfd98c05887b1c1
GitOrigin-RevId: b89cd644834b951ce5b09af1dc1d6df6ce650f26
Change-Id: I31b23c98e03948f6143e3d5f1601ee7aabc6c898
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.