How to safely disable CacheLocality technique if cpu files are not as expected(ppc64le)?

Is it safe to **disable `CacheLocality` technique** by removing the "unable to load cache sharing info" exception at folly/concurrency/CacheLocality.cpp:L164 ?

On our ppc64le machine, the cpu files maybe not as expected on other architectures like x86_64:

The impl expects there is file named "shared_cpu_list" in "/sys/devices/system/cpu/cpu0/cache/index0/"

If no file named "shared_cpu_list" is found, the impl will throw exception:

So is it safe to **disable `CacheLocality` technique** by removing the "unable to load cache sharing info" exception at folly/concurrency/CacheLocality.cpp:L164 ?

Start by reading folly/concurrency/CacheLocality.cpp around line 164 and compare the expected cache files with the ppc64le layout shown in the issue. Determine whether the missing shared_cpu_list should produce a safe fallback or an error, and verify the chosen behavior on the affected platform.

Written by the indexing model from the issue text.