Repository navigation
Conversation
runlevel5
force-pushed
the
powerpc-linux
branch
from
November 19, 2026 23:25
8814cc4 to
57725fb
Compare
Author
|
I have just rebased the work with latest main branch. |
runlevel5
force-pushed
the
powerpc-linux
branch
2 times, most recently
from
November 19, 2026 23:38
7851004 to
7a1769c
Compare
runlevel5
commented
Nov 19, 2026
| case cpuinfo_uarch_power9: | ||
| return "POWER9"; | ||
| case cpuinfo_uarch_power10: | ||
| return "Power10"; |
Author
There was a problem hiding this comment.
Btw, why is it Power10 instead of POWER10? IBM has rebranded it that way
runlevel5
force-pushed
the
powerpc-linux
branch
3 times, most recently
from
November 19, 2026 23:49
6bd1aeb to
425f2cc
Compare
Detect POWER8, POWER9, Power10 and Power11 on PowerPC64 Linux, both little-endian and big-endian: - Vendor, microarchitecture and PVR from /proc/cpuinfo. - Processors, cores and packages from sysfs topology. Linux describes no clusters on PowerPC, so the package is used as the cluster. Offline processors (e.g. SMT threads disabled with ppc64_cpu) are skipped. - Caches from sysfs: size, level, type and the processors sharing each cache. Linux misreports their geometry on POWER (the firmware gives every POWER9 cache 8 "sets" and no L2/L3 line size), so associativity and line size come from a table of documented values for POWER8, POWER9 and Power10, falling back to sysfs. - ISA features from AT_HWCAP and AT_HWCAP2: Power ISA 2.06 to 3.1, AltiVec, VSX, MMA, DFP, IEEE 128-bit floating point, HTM, DARN and vector crypto. Co-authored-by: Trung Lê <8@tle.id.au>
runlevel5
force-pushed
the
powerpc-linux
branch
from
November 19, 2026 23:56
425f2cc to
2a890ac
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Detect POWER8, POWER9, Power10 and Power11 on PowerPC64 Linux, both little-endian and big-endian:
Both endiannesses share the same code. CMake treats
ppc64leasppc64, and Bazel gains alinux_ppc64setting next tolinux_ppc64le.Tested on:
get-current-testpass.init-testfails its two "L2 cache exists" checks, see below.Known limitation: QEMU pseries guests describe only the L1 caches in the device tree (no
l2-cachenodes), so Linux exposes no L2 or L3 in sysfs and cpuinfo reports none. cpuinfo reports what the OS reports here rather than guessing, so the genericinit-test, which expects an L2 cache, fails inside such guests on either endianness.power10-kvm-testcovers this case.Supersedes #267
Fixes #2