On Wed, 9 Apr 2025 03:57:10 GMT, Fei Yang <fy...@openjdk.org> wrote: > > It's not some intermittently failure. The majority of them can't work as > > they use pstack, open core files, use PerfData, etc.. and expected it to be > > rv64. But core files, pstack are in host arch as we are running qemu-user. > > I can remove tests which timeouts and only keep test which simply can't > > work in qemu-user environment in this PR. Seems good? > > Hi, That make sense to me. And it doesn't seem to me to be riscv-specific > issue, but rather one with qemu-user. Maybe we should update the title and > changes to reflect that? I sometimes see people testing with qemu for other > CPU platforms as well like ppc, s390, etc. Guess they might be helped with > this too.
Hey, thanks for considering. The default qemu /proc/cpu do not contain any information about this being qemu. And there is no standard way to find this out AFIAK. Some platforms have target specific /proc/cpu and put qemu in there, but it have no standard format. The whole proc -> uarch string -> jvm cpu string -> jtreg require is qemu/linux-user/riscv specific. ------------- PR Comment: https://git.openjdk.org/jdk/pull/24229#issuecomment-2788434073
