You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to run a benchmark I noticed that the function collect_cpu_freq() in _collect_metadata.py parses the output of /proc/cpuinfo but fails on the IBM Z (mainframe, S/390).
On Linux on IBM Z the output may look like this:
vendor_id : IBM/S390
# processors : 16
[...]
processor 0: version = 00, identification = [...]
cpu number : 0
cpu MHz dynamic : 5208
cpu MHz static : 5208
[...]
The code splits lines starting with processor at ':' which will not yield a proper CPU number on Z. It should suffice, however, to check the vendor_id for IBM/S390 and look for cpu number in this case instead. The parsing of of the frequency should work ok with the existing logic.
The text was updated successfully, but these errors were encountered:
No idea why the email response to this thread did not go through, here it is again:
Unfortunately, it would take me a while to obtain copyright assignment
for a new project :( I already have a fix on my machine that is rather
trivial and works as far as I can tell, I just cannot post it here for
legal reasons. Therefore, I assume it will be faster if you fix it.
When trying to run a benchmark I noticed that the function
collect_cpu_freq()
in_collect_metadata.py
parses the output of/proc/cpuinfo
but fails on the IBM Z (mainframe, S/390).On Linux on IBM Z the output may look like this:
The code splits lines starting with
processor
at ':' which will not yield a proper CPU number on Z. It should suffice, however, to check thevendor_id
forIBM/S390
and look forcpu number
in this case instead. The parsing of of the frequency should work ok with the existing logic.The text was updated successfully, but these errors were encountered: