The state of ARM - a 64bit view of what does/doesn't work State of the Union on ARM - the software, the hardware and anything in between

The AArch64 port is now in pretty good shape with most things ported and built. However we know that there is plenty of software that is not optimised and some may not actually work at all. Please come along and moan about anything you have found which doesn't work as well on AArch64 as it does on x86. We (Linaro, ARM and openSUSE) want your feedback on where to direct effort next.

This talk will cover the current status of the port with both and upstream and openSUSE specific view, and crucially hardware availability. Only a few things are completely missing, but we know that a lot of software is using the basic 'fallback support' where other architectures have specific optimisations. Some stuff is probably building, but not actually working right. We are keen to fix things that are actively getting in the way of using AArch64 in real systems, but to do that we need feedback from users on what to look at next as we move from mostly enablement to mostly optimisation. GCC, OpenJDK, & LLVM are known to be in good shape, but there is a pile of other stuff that probably isn't. It's very hard to test 'all the software in the world', so please tell us about stuff you've noticed not working well, or incredibly slowly, or that you suspect might be a problem and need work.

Transcript

1. The state of ARM® A 64bit view of what does/doesn't work Andrew Wafaa awafaa@opensuse.org/andrew.wafaa@arm.com
2. 2 I am ... • Senior Principal Engineer, Open Source
3. 3 I am ... • Involved with openSUSE for a long time
4. 4 I am ... • Known to have questionable fashion choices
5. 5 I am ... • Known to have questionable fashion choices
6. 6 I am ... • Known to have questionable fashion choices
7. 7 I am ... • European
8. What am I going to talk about?
9. 9 Topics • What is AArch64? ‒ AKA ARM64 • Software Status ‒ What’s built, known to work, optimized, broken, missing • Hardware Status ‒ What can you run your software on • How well does it all work ‒ Benchmarking • Next Steps
10. What is AArch64?
11. 11 What is AArch64 • Known in some parts of the world as ARM64 • Part of the ARMv8 architecture • Designed from the ground up • Cortex-A53/57/72
12. Software Status
13. 13 Mostly Working • Almost everything builds
14. 14 “If it builds, it’s done!” - Anonymous build engineer
15. 15 AArch64 vs x86_64
16. 16 Mostly done • The obvious things people care about are done • Number of things that need porting are much smaller ‒ Those that need porting are harder to port
17. 17 Does it run? • If it has integrated unit tests, then it should run • Much has not been tested • It may not run optimally
18. 18 What’s been optimized? • Languages ‒ C, C++, Java (OpenJDK 8 & 9), Python, Perl, PHP6, Ocaml, Javascript (v8), Haskell (ghc), Lisp, • Compilers ‒ GCC & LLVM • Kernel ‒ Raid6, crypto • Applications ‒ OpenSSL, Ceph, Hadoop, Xen (much smaller codebase)
19. 19 What’s the difference between optimized and non-optimized? • Simple example from our friends at Debian using ‘botch’ • Generic ocaml – 4hrs 52m • Native ocaml – 1hr 15m • X86_64 – 37m
20. 20 Ported but not Optimized • Lua, R, Rust, GoLang, Julia, Perl6, Pascal (fpc), Javascript (Spidermonkey/Ionmonkey), Mono, OpenCV, LibreOffice
21. 21 “Removing is often better than ‘fixing’ ” - Wookey • 1000 bits of assembler: ‒ https://wiki.linaro.org/Platform/DevPlatform/ArmSoftwareLi st ‒ http://performance.linaro.org/
22. 22 What’s missing? • LuaJit to be ported – being worked on ‒ Linaro working with upstream • GoLang SSA backend – being worked on ‒ Expected in GoLang 1.8 • Mono has been ported but not packaged ‒ Most of the unresolvable list are Mono packages
23. Hardware Status
24. 24 No space, no problem • Runabove from OVH ‒ runabove.com using ThunderX • OBS ‒ Mix of Xgene1, Seattle A1100
25. 25 I have space and I like blinky lights • HP Moonshot • ARM Juno • APM C1 • SoftIron Overdrive 1000, 3000 • Gigabyte MP30, D120, H270, R120, R150, R270 • 96 Boards, HiKey, Dragonboard, Cello • Pine64 • RaspberryPi 3
26. 26 How much for your blinky lights? • $10,000+ ‒ HP Moonshot
27. 27 How much for your blinky lights? • $5,000+ ‒ Gigabyte H270
28. 28 How much for your blinky lights? • $3,000 ‒ Gigabyte R270
29. 29 How much for your blinky lights? • $2,500 ‒ SoftIron Overdrive 3000
30. 30 How much for your blinky lights? • $2,500 ‒ Applied Micro XC1
31. 31 How much for your blinky lights? • $2,500 ‒ Gigabyte R150
32. 32 How much for your blinky lights? • $2,000 ‒ Gigabyte R120
33. 33 How much for your blinky lights? • $1,000 ‒ Gigabyte MP30
34. 34 How much for your blinky lights? • $600 ‒ SoftIron Overdrive 1000
35. 35 How much for your blinky lights? • $300 ‒ 96Boards Cello
36. 36 How much for your blinky lights? • $75 - $99 ‒ 96Boards HiKey (1G/2G)
37. 37 How much for your blinky lights? • $75 ‒ 96Boards Dragonboard 410C
38. 38 How much for your blinky lights? • $35 ‒ RaspberryPi 3
39. 39 How much for your blinky lights? • $15 - $30 ‒ Pine64 (0.5G/1G)
40. Benchmarking
41. 41 Benchmarking is difficult • Too easy to game • Need roughly equivalent platforms • Need to look for changes over a period of time • Need to pick a real & common metric • If you know of good benchmarks let me know!
42. Questions?
43. Thank you. Join the conversation, contribute & have a lot of fun! www.opensuse.org
44. 44 Have a Lot of Fun, and Join Us At: www.opensuse.org
45. General Disclaimer This document is not to be construed as a promise by any participating organisation to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. openSUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for openSUSE products remains at the sole discretion of openSUSE. Further, openSUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All openSUSE marks referenced in this presentation are trademarks or registered trademarks of SUSE LLC, in the United States and other countries. All third-party trademarks are the property of their respective owners. License This slide deck is licensed under the Creative Commons Attribution-ShareAlike 4.0 International license. It can be shared and adapted for any purpose (even commercially) as long as Attribution is given and any derivative work is distributed under the same license. Details can be found at https://creativecommons.org/licenses/by-sa/4.0/ Credits Template Richard Brown rbrown@opensuse.org Design & Inspiration openSUSE Design Team http://opensuse.github.io/branding- guidelines/