From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: chainlint test failing on Linux sparc64
Date: Mon, 20 May 2024 12:02:34 +0200 [thread overview]
Message-ID: <7acbd5c6c68bd7ba020e2d1cc457a8954fd6edf4.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <CAPig+cQLsUTpjiZ_TXh2GJAS=tJScUWYxiuR87rtwdTu8H9PXw@mail.gmail.com>
Hi Eric,
On Mon, 2024-05-20 at 05:58 -0400, Eric Sunshine wrote:
> On Mon, May 20, 2024 at 5:36 AM Eric Sunshine <sunshine@sunshineco.com> wrote:
> > My suspicion is that "actual" will have size 0 for you. If that's the
> > case, I'd suggest running the commands from the "check-chainlint"
> > target in t/Makefile manually one at a time to see if you can figure
> > out which is failing. For instance:
> >
> > % ./chainlint.pl --emit-all chainlinttmp/tests
>
> This reminded me of an earlier report in which chainlint.pl was
> producing no output for "actual" on Linux for s390x processors. That
> was due to /proc/cpuinfo producing results which the script wasn't
> expecting. It was fixed by 1f51b77f4f (chainlint.pl: fix /proc/cpuinfo
> regexp, 2022-11-22)[1]. At the time of that patch, I noted[2]:
Yeah, the output for /proc/cpuinfo is not standardized across architectures,
unfortunately.
> A separate problem is that chainlint.pl doesn't fall back to a
> sensible non-zero value if ncores() returns 0 (or some other
> nonsense value). That is, of course, outside the scope of the
> well-focused problem fix which this standalone patch addresses. I
> may end up submitting a fix separately to make it fall back
> sensibly.
>
> which probably explains the behavior you're experiencing. To fix it,
> we'll need to see the output you get from:
>
> cat /proc/cpuinfo
Here you go:
glaubitz@stadler:~$ cat /proc/cpuinfo
cpu : UltraSparc T4 (Niagara4)
fpu : UltraSparc T4 integrated FPU
pmu : niagara4
prom : OBP 4.38.16 2018/11/28 07:24
type : sun4v
ncpus probed : 48
ncpus active : 48
D$ parity tl1 : 0
I$ parity tl1 : 0
cpucaps :
flush,stbar,swap,muldiv,v9,blkinit,n2,mul32,div32,v8plus,popc,vis,vis2,ASIBlkInit,fmaf,vis3,hpc,ima,pause,cbcond,aes,des,kasumi,camellia,md5,sha1,sha256,sha512,mpmul,montmul,montsqr,crc32c
Cpu0ClkTck : 00000000a9beeee4
Cpu1ClkTck : 00000000a9beeee4
Cpu2ClkTck : 00000000a9beeee4
Cpu3ClkTck : 00000000a9beeee4
Cpu4ClkTck : 00000000a9beeee4
Cpu5ClkTck : 00000000a9beeee4
Cpu6ClkTck : 00000000a9beeee4
Cpu7ClkTck : 00000000a9beeee4
Cpu8ClkTck : 00000000a9beeee4
Cpu9ClkTck : 00000000a9beeee4
Cpu10ClkTck : 00000000a9beeee4
Cpu11ClkTck : 00000000a9beeee4
Cpu12ClkTck : 00000000a9beeee4
Cpu13ClkTck : 00000000a9beeee4
Cpu14ClkTck : 00000000a9beeee4
Cpu15ClkTck : 00000000a9beeee4
Cpu16ClkTck : 00000000a9beeee4
Cpu17ClkTck : 00000000a9beeee4
Cpu18ClkTck : 00000000a9beeee4
Cpu19ClkTck : 00000000a9beeee4
Cpu20ClkTck : 00000000a9beeee4
Cpu21ClkTck : 00000000a9beeee4
Cpu22ClkTck : 00000000a9beeee4
Cpu23ClkTck : 00000000a9beeee4
Cpu24ClkTck : 00000000a9beeee4
Cpu25ClkTck : 00000000a9beeee4
Cpu26ClkTck : 00000000a9beeee4
Cpu27ClkTck : 00000000a9beeee4
Cpu28ClkTck : 00000000a9beeee4
Cpu29ClkTck : 00000000a9beeee4
Cpu30ClkTck : 00000000a9beeee4
Cpu31ClkTck : 00000000a9beeee4
Cpu32ClkTck : 00000000a9beeee4
Cpu33ClkTck : 00000000a9beeee4
Cpu34ClkTck : 00000000a9beeee4
Cpu35ClkTck : 00000000a9beeee4
Cpu36ClkTck : 00000000a9beeee4
Cpu37ClkTck : 00000000a9beeee4
Cpu38ClkTck : 00000000a9beeee4
Cpu39ClkTck : 00000000a9beeee4
Cpu40ClkTck : 00000000a9beeee4
Cpu41ClkTck : 00000000a9beeee4
Cpu42ClkTck : 00000000a9beeee4
Cpu43ClkTck : 00000000a9beeee4
Cpu44ClkTck : 00000000a9beeee4
Cpu45ClkTck : 00000000a9beeee4
Cpu46ClkTck : 00000000a9beeee4
Cpu47ClkTck : 00000000a9beeee4
MMU Type : Hypervisor (sun4v)
MMU PGSZs : 8K,64K,4MB,256MB,2GB
State:
CPU0: online
CPU1: online
CPU2: online
CPU3: online
CPU4: online
CPU5: online
CPU6: online
CPU7: online
CPU8: online
CPU9: online
CPU10: online
CPU11: online
CPU12: online
CPU13: online
CPU14: online
CPU15: online
CPU16: online
CPU17: online
CPU18: online
CPU19: online
CPU20: online
CPU21: online
CPU22: online
CPU23: online
CPU24: online
CPU25: online
CPU26: online
CPU27: online
CPU28: online
CPU29: online
CPU30: online
CPU31: online
CPU32: online
CPU33: online
CPU34: online
CPU35: online
CPU36: online
CPU37: online
CPU38: online
CPU39: online
CPU40: online
CPU41: online
CPU42: online
CPU43: online
CPU44: online
CPU45: online
CPU46: online
CPU47: online
glaubitz@stadler:~$
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2024-05-20 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 7:56 chainlint test failing on Linux sparc64 John Paul Adrian Glaubitz
2024-05-20 8:21 ` Eric Sunshine
2024-05-20 8:24 ` John Paul Adrian Glaubitz
2024-05-20 9:04 ` John Paul Adrian Glaubitz
2024-05-20 9:36 ` Eric Sunshine
2024-05-20 9:56 ` John Paul Adrian Glaubitz
2024-05-20 9:58 ` Eric Sunshine
2024-05-20 10:02 ` John Paul Adrian Glaubitz [this message]
2024-05-20 11:02 ` John Paul Adrian Glaubitz
2024-05-20 16:04 ` Junio C Hamano
2024-05-20 16:07 ` John Paul Adrian Glaubitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7acbd5c6c68bd7ba020e2d1cc457a8954fd6edf4.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).