Recently I started one project: AArch64 SoC features table
The goal is to collect /proc/cpuinfo dumps from misc AArch64 systems and generate table showing which cpu core features are supported in which SoCs.
Handy if you want to play with SVE, SME or other feature you read about in Arm architecture announcements.
Table is visible at [1] page. I also have a blog post [2] listing cpu features supported by Linux.
To make it more useful I need help from other people - power on your aarch64 systems and fill an issue [3] on github please.
1. https://marcin.juszkiewicz.com.pl/download/tables/arm-socs.html
2. https://marcin.juszkiewicz.com.pl/2022/11/08/from-a-diary-of-aarch64-porter-...
3. https://github.com/hrw/arm-socs-table/issues/new?template=new-arm-soc.md
Hi Marcin,
What a great idea!
Interesting for me as I was just working on a bug where VFP stopped being reported to userspace for aarch32 mode in v6.1-rcs due to a rework in the kernel.
That re-work happened in https://lore.kernel.org/all/20220909165938.3931307-2-james.morse@arm.com and the fix for aarch32 being reported incorrectly went in here https://lore.kernel.org/linux-arm-kernel/20221103082232.19189-1-amit.kachhap...
But in short it may also be useful to capture the kernel version you tested in the table, as what is reported to userspace could change a bit especially with the latest v6.1 kernel.
I wonder also if capturing aarch32 features for each SoC is also worthwhile? You can use getauxval(AT_HWCAP2) api for that. See this link for more info https://community.arm.com/arm-community-blogs/b/operating-systems-blog/posts...
regards,
Peter.
On Tue, 15 Nov 2022 at 12:55, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
Recently I started one project: AArch64 SoC features table
The goal is to collect /proc/cpuinfo dumps from misc AArch64 systems and generate table showing which cpu core features are supported in which SoCs.
Handy if you want to play with SVE, SME or other feature you read about in Arm architecture announcements.
Table is visible at [1] page. I also have a blog post [2] listing cpu features supported by Linux.
To make it more useful I need help from other people - power on your aarch64 systems and fill an issue [3] on github please.
https://marcin.juszkiewicz.com.pl/2022/11/08/from-a-diary-of-aarch64-porter-...
linaro-dev mailing list -- linaro-dev@lists.linaro.org To unsubscribe send an email to linaro-dev-leave@lists.linaro.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
W dniu 16.11.2022 o 10:26, Peter Griffin pisze:
What a great idea!
Thanks!
Interesting for me as I was just working on a bug where VFP stopped being reported to userspace for aarch32 mode in v6.1-rcs due to a rework in the kernel.
That re-work happened in https://lore.kernel.org/all/20220909165938.3931307-2-james.morse@arm.com and the fix for aarch32 being reported incorrectly went in here https://lore.kernel.org/linux-arm-kernel/20221103082232.19189-1-amit.kachhap...
But in short it may also be useful to capture the kernel version you tested in the table, as what is reported to userspace could change a bit especially with the latest v6.1 kernel.
Random ones as those entries are contributed by random people. Some were taken from online forums even.
I wonder also if capturing aarch32 features for each SoC is also worthwhile? You can use getauxval(AT_HWCAP2) api for that. See this link for more info https://community.arm.com/arm-community-blogs/b/operating-systems-blog/posts...
I base table only on /proc/cpuinfo dump. This way everyone has easy way to provide additional entries. Learnt that hard way with one of my previous projects.
If you require people to run some binary then even providing sources gets people suspicious.