| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
configs: Remove old boot files Most of these "rcS" scripts are only useful for specific disk images that have long been lost to the gem5 community. This commit deletes all of these scripts. It keeps the generally useful hack_back_cktp script and the bbench scripts that work with the android images that are still available. In the future, these remaning scripts should be moved to the gem5 resources repository. Issue-on: https://gem5.atlassian.net/browse/GEM5-350 Change-Id: Iba99e70fde7f656e968b4ecd95663275bd38fd6e Signed-off-by: Jason Lowe-Power <jason@lowepower.com> Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/28507 Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Maintainer: Jason Lowe-Power <power.jg@gmail.com> Tested-by: kokoro <noreply+kokoro@google.com> | 6 年前 | |
configs: Fix tuple unpacking error in Simulation.py with fast-forward (#2800) **Description** This PR fixes a bug where se.py crashes with an AttributeError: 'tuple' object has no attribute 'numThreads' when running with the --fast-forward option. **Root Cause** In configs/common/Simulation.py, the setCPUClass function returns a tuple of (AtomicSimpleCPU, O3CPU) when fast-forwarding is enabled. However, inside the function, the return value from getCPUClass (which is (TmpClass, test_mem_mode)) was assigned to a single variable TmpClass without unpacking. This caused TmpClass to become a nested tuple, leading to the crash downstream in se.py. **Fix** I corrected the logic in Simulation.py to properly unpack the returned values from getCPUClass into TmpClass and test_mem_mode. **Verification** Tested with se.py and --fast-forward option. The simulation now runs without the AttributeError. Signed-off-by: IVIN <109740530+ivin1@users.noreply.github.com> | 6 个月前 | |
config: Use RiscvSystem in riscv/fs_linux.py Change-Id: Id3de4c6aac2b0a75ed0a57bcab5e6261ea83c856 | 9 个月前 | |
misc: Run pre-commit run --all-files This is reflect the updates made to black when running pre-commit autoupdate. Change-Id: Ifb7fea117f354c7f02f26926a5afdf7d67bc5919 | 2 年前 | |
configs, dev, learning-gem5, python, tests: more clarification This commit contains the rest of the base 2 vs base 10 cache/memory size clarifications. It also changes the warning message to use warn(). With these changes, the warning message should now no longer show up during a fresh compilation of gem5. Change-Id: Ia63f841bdf045b76473437f41548fab27dc19631 | 1 年前 | |
后续 phase 我已经开始推进到 Phase 5: gem5 真实 fault injector，但目前还在一个“代码已落地、真实验证待完成”的中间状态。 这轮已经完成的代码方向是： - 在 gem5 里为 CPU 侧增加最小注入接口准备： - gem5/src/cpu/BaseCPU.py - gem5/src/cpu/base.hh - gem5/src/cpu/base.cc - 升级 fault request 合同： - gem5/configs/example/arm/sdc_fault_request.py - 开始把 sdc_kunpeng920_se.py 改成“可脚本化真实注入”的模式： - 解析 fault_target - 判断 implemented_in_script - 预留“先 simulate 到 fault_tick，再注入，再继续 simulate”的路径 我还专门做了运行时探针，确认了几件关键事实： - System / ArmSystem 的 Python 层没有直接暴露 threads - SimpleBoard 路径下拿到的是 stdlib board，不适合直接从 root.system 做注入 - stdlib processor/core 可以拿到 BaseCPU simobject，这也是我把真实注入接口转移到 BaseCPU 的原因 当前真正的阻塞点不是设计，而是 gem5 需要一次完整增量重编来把新的 pybind/C++ 方法带进 gem5.opt。我已经找到能让它通过 Python 检查的构建组合： - CC=/usr/bin/cc - CXX=/usr/bin/c++ - PYTHON_CONFIG=/opt/homebrew/bin/python3-config - 同时清掉 conda 的交叉编译环境变量 这轮编译已经不再卡在 Python embed 检查，而是在正常进行全树增量重建，但还没有等到最终链接完成，所以我还不能诚实地说 Phase 5 已真实验证通过。 当前状态可以总结为： - Phase 2：真实端到端已通过 - Phase 4：真实多 fault campaign 已通过 - Phase 5：实现已开始，验证前最后一步是等 gem5.opt 重编完成，再跑“真实寄存器位翻转注入”验证 如果你继续，我下一步就只做一件事：盯住 gem5 编译完成，然后立刻跑 Phase 5 的真实注入 probe。 Signed-off-by: WangxuMarshall <wangxumarshall@qq.com> Entire-Checkpoint: 6bde5bb60541 | 3 个月前 | |
misc: bump precommit black and isort versions (#1971) This PR bumps the versions of black and isort in .pre-commit-config.yaml to 25.1.0 and 6.0.0, respectively, as a number of unrelated commits were added to https://github.com/gem5/gem5/pull/1969 when its target branch was switched from stable to develop. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> | 1 年前 | |
configs,stdlib,tests: Remove get_runtime_isa() (#241) get_runtime_isa() has been deprecated for some time. It is a leftover piece of code from when gem5 was compiled to a single ISA and that ISA used to configure the simulated system to use that ISA. Since multi-ISA compilations are possible, get_runtime_isa() should not be used. Unless the gem5 binary is compiled to a single ISA, a failure will occur. The new proceedure for specify which ISA to use is by the setting of the correct BaseCPU implementation. E.g., X86SimpleTimingCPU of ArmO3CPU. This patch removes the remaining get_runtime_isa() instances and removes the function itself. The SimpleCore class has been updated to allow for it's CPU factory to return a class, needed by scripts in "configs/common". The deprecated functionality in the standard library, which allowed for the specifying of an ISA when setting up a processor and/or core has also been removed. Setting an ISA is now manditory. Fixes #216. | 2 年前 | |
configs, dev, learning-gem5, python, tests: more clarification This commit contains the rest of the base 2 vs base 10 cache/memory size clarifications. It also changes the warning message to use warn(). With these changes, the warning message should now no longer show up during a fresh compilation of gem5. Change-Id: Ia63f841bdf045b76473437f41548fab27dc19631 | 1 年前 | |
configs: Allow GPU-FS to use HBMCtrl memory controller (#2425) This commit adds a command line argument --hbm-ctrl to enable HBMCtrl in GPU-FS. HBM_2000_4H_1x64 is tested. | 11 个月前 | |
configs, dev, learning-gem5, python, tests: more clarification This commit contains the rest of the base 2 vs base 10 cache/memory size clarifications. It also changes the warning message to use warn(). With these changes, the warning message should now no longer show up during a fresh compilation of gem5. Change-Id: Ia63f841bdf045b76473437f41548fab27dc19631 | 1 年前 | |
misc: Run pre-commit run --all-files This ensures isort is applied to all files in the repo. Change-Id: Ib7ced1c924ef1639542bf0d1a01c5737f6ba43e9 | 2 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 6 年前 | ||
| 6 个月前 | ||
| 9 个月前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 3 个月前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 11 个月前 | ||
| 1 年前 | ||
| 2 年前 |