Comment 23 for bug 2019203

I've confirmed, on Amazon Linux 2 with AWS Graviton2 CPU (arm64), that the same workaround as for s390x should be viable, namely reading from sysfs:

$ grep -n '' /sys/devices/system/cpu/cpu*/cache/index*/coherency_line_size
/sys/devices/system/cpu/cpu0/cache/index0/coherency_line_size:1:64
/sys/devices/system/cpu/cpu0/cache/index1/coherency_line_size:1:64
/sys/devices/system/cpu/cpu0/cache/index2/coherency_line_size:1:64
/sys/devices/system/cpu/cpu0/cache/index3/coherency_line_size:1:64
/sys/devices/system/cpu/cpu1/cache/index0/coherency_line_size:1:64
/sys/devices/system/cpu/cpu1/cache/index1/coherency_line_size:1:64
/sys/devices/system/cpu/cpu1/cache/index2/coherency_line_size:1:64
/sys/devices/system/cpu/cpu1/cache/index3/coherency_line_size:1:64

$ cat /proc/cpuinfo
processor : 0
BogoMIPS : 243.75
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x3
CPU part : 0xd0c
CPU revision : 1

processor : 1
BogoMIPS : 243.75
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x3
CPU part : 0xd0c
CPU revision : 1