Hi all,
I want to extract trace about Ruby, so i use --debug-flags=Ruby. But when i
use it and script in FS,it couldn't work and appear errors.errors as follow:
Program aborted at tick 2508906376500
--- BEGIN LIBC BACKTRACE ---
Update:
It appears that the issue I was having with jiffies was misdirection...of
another issue that I was able to workaround but not specifically identify.
The problem was that I was using work queues to schedule a delayed task at
a fixed period. However, whatever timer that the work queue was
All,
I wanted to simulate a Processing in Memory(PIM) environment using GEM5.
Does GEM5 support PIM feature?
If yes, please share the appropriate resource to use it. If no, is this a
feature in pipeline to be added to GEM5 ?
Thanking You,
Aviral Khattar
New versions of gem5 also auto-generate DTBs. This requires support from the
simulation script, but that should already be implemented for the
configurations in configs/example/arm/ and fs.py. The latter might requires
that --generate-dtb is specified to enable this. Keep in mind that the
dear all,i run the following code on gem5 with ubunto operating system and
execute the command and i receive errorĀ comes below. could you please help.
REGARDSM.ETEMAD
source code
import m5
from m5.objects import *
system=System()
Hi Jason,
Thank you for your suggestions. Checking the output for smaller programs
helped and the benchmarks are working fine now.
And regarding tracking the referred blocks in the cache, I tracked the
blocks that are referred in the recvTimingReq function. When I dug through
the code, I could
Hi all,
I am trying to simulate the GDDR5 model (GDDR5_4000_2x32) in
src/mem/DRAMCtrl.py and I am facing with the assertion below
*gem5.opt: build/ARM/mem/dram_ctrl.cc:2107: void
DRAMCtrl::Rank::processWakeUpEvent(): Assertion `(pwrState == PWR_ACT_PDN)
|| (pwrState == PWR_PRE_PDN) ||
Hi,
dist-gem5 does not support delayed checkpoint currently. The delay option is
used to decide whether a 'collective' or an 'immediate' checkpoint is to be
taken.
If delay == 0 then the checkpoint is triggered only when all gem5 instances
(participating in the dist-gem5 run) have completed