-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gem5.opt 执行 checkpoint 时 Difftest failed #184
Comments
Is it related to RV-H @jueshiwenli ? |
can you show me the nemu config? |
He says he is using riscv64-gem5-ref_defconfig of cf24515c85f5be898687959ab299ea276dbd7c56 |
the config need update, open RVH, i will update it in nemu later |
This looks more like checkpoint and gcpt restore was not loaded correctly |
谢谢你的回答,我根据你的描述尝试了 “Jul 24, 2024 release” 中的 "gcb-restorer.bin + nemu-gcbv-ref.so" 和 “gcbv-restorer.bin + nemu-gcbv-ref.so” 这两个组合,得到的还是同样的错误。我还对 Releases 中已经编译好的其他文件进了尝试,具体可见上面的 “现象描述” 。之后我会更新 NEMU 仓库后重新尝试,希望能成功。 |
环境描述:
GEM5:xs-dev f231aa5
NEMU:master cf24515c85f5be898687959ab299ea276dbd7c56
DRAMsim3:master 29817593b3389f1337235d63cac515024ab8fd6e
LibCheckpointAlpha:main c5c2fef74133fb2b8ef8642633f60e0996493f29
工具链:15.0.0(/nfs/home/hebo/TOOL/gnu-riscv64-toolchain/riscv-toolchain-gcc15-240613-noFFnoSeg2)
我遇到的问题:gem5.opt 执行 checkpoint 时 Difftest failed
我想要的:我想用最新的 GEM5 跑我的 checkpoint(gcb)
现象描述
在用 gem5.opt 执行 checkpoint 时 Difftest failed ,部分日志如下所示:
感觉像是我的 difftest 启动失败了,我怀疑是我 riscv64-nemu-interpreter-so 或者 gcpt.bin 有问题,于是我尝试使用 GEM5/releases 里的编译好的文件:
riscv64-nemu-interpreter-4332a525-so + 我自己的 gcpt.bin ,出现同样的现象
nemu-gcbv-ref.so + gcb-restorer.bin ,出现同样的现象
riscv64-nemu-interpreter-so + gcpt.bin ,出现同样的现象
nemu-gcbv-ref.so + gcb-restorer.bin ,出现同样的现象
riscv64-nemu-interpreter-231008.so + gcpt-restorer-231016.bin ,出现如下所示的现象,但还是没跑起来:
到这里我开始怀疑是我 checkpoint 有问题,于是我使用了我很久以前配置的 GEM5 跑同一个 checkpoint 文件,它是可以执行的。
如何构建的 GEM5
GEM5 build
NEMU build
完整的执行命令
完整的日志信息
额外的信息
这是我很久之前配置的 GEM5 跑同一个 checkpoint 文件,它是可以执行的。
执行命令:
日志文件路径:/nfs/home/hebo/TOOL/GEM5/test/log.txt
The text was updated successfully, but these errors were encountered: