Hi Malik,
Thanks for taking a look at this!
On Sat, Sep 19, 2026 at 12:54:38PM +0300, Malik Mlitat wrote:
> Two things I could use your help with.
>
> First, a test fixture. Upstream keeps one test file per architecture
> (tests/test_linux_aarch64_64.py, tests/test_linux_fedora_5_s390x.py and so
> on), and there's no Alpha equivalent yet. Could you send the output of
>
> cat /proc/cpuinfo
Attached proc-cpuinfo.txt for an Alpha ES45 with 2 cpus.
> from the machine you tested on, plus
>
> python3 -c "import cpuinfo, json; print(json.dumps(cpuinfo.get_cpu_info(),
> indent=2))"
Attached python-cpuinfo-output.txt with the requested output
> Second, has this been sent upstream? The patch is currently marked
> Forwarded: no. Upstream is https://github.com/workhorsy/py-cpuinfo and a
> pull request there would spare Debian carrying this indefinitely. Happy to
> open it myself with you as the author if you'd rather not.
No, I hadn't pushed it upstream, partly upstream seemed to be somewhat
dead, but even more so because I don't have a github account.
I'm happy for you to push it upstream if you are happy to do so.
Regards,
Michael.
cpu : Alpha
cpu model : EV68CB
cpu variation : 7
cpu revision : 0
cpu serial number : JA31800791
system type : Titan
system variation : Privateer
system revision : 0
system serial number : AY32202587
cycle frequency [Hz] : 1250000000
timer frequency [Hz] : 1024.00
page size [bytes] : 8192
phys. address bits : 44
max. addr. space # : 255
BogoMIPS : 2480.92
kernel unaligned acc : 0 (pc=0,va=0)
user unaligned acc : 92 (pc=1202a56d8,va=20009a80013)
platform string : AlphaServer ES45 Model 1
cpus detected : 2
cpus active : 2
cpu active mask : 0000000000000003
L1 Icache : 64K, 2-way, 64b line
L1 Dcache : 64K, 2-way, 64b line
L2 cache : n/a
L3 cache : n/a
{
"python_version": "3.14.7.final.0 (64 bit)",
"cpuinfo_version": [
9,
0,
0
],
"cpuinfo_version_string": "9.0.0",
"arch": "ALPHA",
"bits": 64,
"count": 2,
"arch_string_raw": "alpha",
"hardware_raw": "AlphaServer ES45 Model 1",
"brand_raw": "EV68CB",
"hz_advertised_friendly": "1.2500 GHz",
"hz_actual_friendly": "1.2500 GHz",
"hz_advertised": [
1250000000,
0
],
"hz_actual": [
1250000000,
0
]
}
