add cpuinfo for loongarch64

[zhangwenlong8911]

No description provided.

[zhangwenlong8911]

@SuperQ Hello, I added cpuinfo for loongarch64, at the same time I have compiled and tested locally, and have used the codes in other projects without any problems. can you help me to review the code? Thank you

[SuperQ]

Thanks, I'll take a look at this soon.

[discordianfish]

Oh exciting! I don't think it's possible to get loongarch64 systems anywhere yet, right? Or do you know a way? So I can't really verify this..

[zhangwenlong8911]

loongarch64 is a new system, and command “make test” in loongarch64 is ok, I can provide a screenshot of the result

[xen0n]

The LoongArch kernel support hasn't been upstream yet; even the first submission is yet to appear. So in theory the /proc/cpuinfo format could change; I suggest we wait for the moment, and only revise and merge after the kernel bits get upstreamed.

[discordianfish]

I'm fine either way, merging this also wouldn't break anything so..

@zhangwenlong8911 Do you know if I can buy a loongarch64 system somewhere online? Or how did you get your hands on one?

[xen0n]

FYI, the initial LoongArch kernel bits appeared; but it's still long before being mainlined, so technically things could still change. For now the /proc/cpuinfo format is very much MIPS-like, and I doubt it would persist into the final version.

[zhangwenlong8911]

@discordianfish I am a member of the loongarch64 team, so I can get first-hand information, LoongArch kernel support has been submitted to the kernel community

[xen0n]

Aren't we using "loong/loong64" everywhere in the Go land instead of "loongarch/loongarch64"? Plus the /proc/cpuinfo format issue hasn't settled yet. We really should wait a bit longer.

[discordianfish]

+1 for consistency, if it's called 'loong(64)' in golang, let's do it here as well.

[zhangwenlong8911]

I think you are right@xen0n @discordianfish, I modify the architecture information now, about / proc / cpuinfo, let's wait

[xen0n]

Please make sure to test your code on multiple arches (at least test amd64 too, in your case).

[xen0n]

Finally, please add Signed-off-by line. (see that failing DCO check?)

While at it, modify your PR title and commit message so LoongArch64 is uniformly referred to as loong64 in the Go ecosystem.

[discordianfish]

LGTM

[SuperQ]

Go 1.19 finally supports this platform.